Why Single-Page Web Application [closed] - asp.net

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
While Single-Page application approach is rising as a web development choice, I still don't understand, practically, how would losing the ability to go back/forward in the browser be an O.K sacrifice? Imagine Facebook without direct page navigation! Is there an essential/direct purpose for SPA I can't get my hands on?

You wont have to give up back button functionality to develop a single page application. HTML5 has a history api (and there's polyfills for older browsers) which allows your to keep back button functioning properly.
The main reason (in my opinion) to go for a single page approach is the more app-like feel it gives you. For example gmail feels more like an app than a web page, and given its purpose, I think that's way it should be too. Another example might be the pixlr online image editor.
Single page approach indeed doesn't suit every purpose, but when you want a webapp to feel just that, instead of a website, then single page might be the way to go.
You mentioned direct navigation in comments, and that's totally doable if it's something that makes sense in your context. Angularjs can do that, and I'm sure pretty much every modern single page framework has a way of implementing this.

Related

What do you use to make javascript more C#-like? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm starting a new ASP.Net based project using javascript, JQuery etc on the browser.
I'm no expert at javascript and (after years of C# etc) get annoyed with its unstructured, typeless nature, no class hierarcy, everything global, etc. (It may not really be as bad as it sometimes feels!)
I'm aware there's various projects about to make javascript 'better' - things like knockoutjs, typescript, node.js and others - and I'm sure they all have their strengths and weaknesses, and probably one can use combinations of them.
I'm interested to know people's experiences and recommendations for what to use to make the javascript side of ASP.Net programming a little more structured (more like C#?) without too much of a learning curve.
Well first of all as javascript syntax is C-like you can write it in such a way that code will look like C. For instance check source code for asp.net ajax library.
Second, there is number of projects which were aimed to help write C# code that is translated to Javascript, that can help you as a starting point. Check http://sharpkit.net/ for that.
But regardless of what you are going to use you absolutely have to understand how javascript works in browser, what is DOM, what facilities window, document and navigator gives you etc etc
I belive that is your main problem, after all, it is really easy to learn how to use namespaces in javascript and bring structure to your code.
Also typescript that you mentioned in comments is really good at making code cleaner and more structured. It also adds classes and inheritance and types and some other cool features that you miss in language again.
So to sum up - you have to learn browser environment, the same way you have to learn .net classes on top of knowing c#-language. You can learn some easy tricks like AMD/require.js/js-namespaces to bring structure to your code, or since you are new and came from .net world - just adopt typescript.

Classic ASP to ASP.NET MVC [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am currently working with a classic asp application. We are looking to upgrade this in small phases to .NET. what I mean by small phases is page by page over an extended period of time.
I want to minimize impact to users. So upgrade pages but keeping the look the same for now. The classic asp app is all frames based so I think i could keep the look and run the upgraded page and point to the new page?
My questions are, what is the best method in doing this in peoples experience? Again I want to build this in .NET so I don't know if i would be best off using MVC or asp.net? would utilizing a particular framework make any difference here?
Those folks who have went through this pain in the past what were some gotchyas in upgrading and running a newer technology with an older technology? I would imagine i shouldn't have to much heartache in running these together.
Any additional things we should think about?
Thanks for the assistance.
MVC provides more control and flexibility. You can use .cshtml page to insert html code and use model variables (#Model.xxx with Razor) defined in your .cs code. You can easily display list box, combo box and other controls. Besides it does not require AJAX.

What do we call a person who is creating layouts for webpages? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
For a few days now i am looking for a webdesigners who can make my page look nice. All i can find is people that are making .psd files of websites so i can cut out elements and put them on my page. I don't need that. I want someone, who will visit my page, look through my .css file, remake it, and maybe add few graphic elements on site - like logo and/or some icons.
I would do it by myself, but i am very bad at selecting/coupling colors, so i need someone to do it for me.
So, reasuming: how do i search through google to actually find people that can make my page look good by remaking my .css files?
People still go by the umbrella term Web Designers : http://www.hanselman.com/blog/HireAndPayADesignerAndBeHappy.aspx
I generally search css web designers to narrow it down.
Altho this area may seem gray there are a few professionals involved on different aspects of what you want.
The reason behind the confusion is that the same professional might occupy more than one role.
A Web Designer should be be able to do that. And it is required of one the basic knowledge of CSS/HTML alongside with your description.
A Web Ui Engenier is the specialist on CSS/HTML/JavaScript he wont design the interface per say He is the guy who implements it.
And a Web UX Designer is the person who will design the user interface and experience. How it should behave and the UI engenier will implement it.

Solve lack of SEO in Silverlight with ASP.net [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Can we combine Silver-light with Asp.net to implement SEO? I mean i want to Program with ASP.net and if i need Animation i use Silver-light? Because i think it can help to find site with Search Engin, is it right?
There are 2 types of silverlight applications.
1) Full blown silverlight application - The entire UI is written with silverlight.
2) Island of Richness application - In this scenario Silverlight is used to enhance a specific part of an application with Rich UI. Commone scenarios include video players, data grids, or more complex animations.
So to answer your question yes this is completely possible.
Silverlight is not search engine friendly regardless if you use ASP.NET or not. Search engines can not read the information in Silverlight so it essentially doesn't exist as far as the search engines are concerned. If you want the information displayed by Silverlight to be found and indexed by the search engines you will need to provide an alternative means of displaying that content. This is usually done by placing HTML within the <object> tag used to display Silverlight content. It is only shown when Silverlight is not available in a browser and search engines can see it just fine. (It's basic accessibility).
SEO of Silverlight sites is certainly doable (ignore anyone that still says it is not),
SEO on a Silverlight website
First ensure that you provide a sitemap for the searchengines. That should map to all content pages.
Provide a parallel ASP.Net website to publish your content for the search engines to read. This is now quite easy with RIA services as an ASP.Net website can consume a RIA service just like any other WCF service.
Make good use of headers, meta tags, titles, human-readable urls to include relevant keywords

How to make maintaince document for a website? [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How to make maintenance document for a website? I've created a site using XHTML ,CSS, jQuery etc. it's big site.
Now i have to write a maintenance document for a site for if any changes comes in future related to design, content and functionality then those things will be handled by someone else.
How and what should i keep in maintenance document.
Your maintenance document should contain a high-level design of what each file contains and the general code structure of the project.
For example, if you wrote some javascript to handle certain events, document those and how they interact with the page.
You should also document any logical groupings you've made. If a folder contains all the XHTML for a certain topic, write those down.
Also give a brief explanation of how you used CSS to layout the page. Which classes are where on the page, and which classes or ids are important.
As for the how, I like to set up a Wiki in such cases, for example DokuWiki. They're easy to understand, and in case of DokuWiki there's no database involved, just plain text files.
As to what, (in addition to what Ben S nicely outlines in his answer) I'd cover
The basic technologies used
Any client-side libraries used and their versions
A rundown on the directory structure
The hosting environment, what is configured where, control panel URLs and the like (never actual passwords)
Names and contact data of contacts (Tech support, etc.) plus any experiences with them (how best to reach them, phone, mail, etc.)

Resources