As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
How do you define ONE asp.net application? Does it have to be built under one solution or does it have to be deployed under one application under IIS?
Can multiple web projects be deployed under one IIS application (so that they have access to each other's session, cache etc) ?
This is just a theoretical question.
Update: What I am stressing on is what makes it ONE application.
An application is how it is deployed under IIS. One application can consist of multiple projects but under IIS , all projects will combine to come out as an application.
If for one some reason, a website was divided across two solutions but during deployment it gets into one website under IIS then that's really one application and two solutions.
Saying all that , a lot of it depends on how you and your team uses this terminology. There is no black and white rule here.
I define an asp.net application as any web application that has been built primarily using asp.net as the technology behind it.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I'm gonna start developing a single page web application using Microsoft stack. In some critical parts of the project I have to provide real time data.
I can use Signalr or Web Sockets for these kind of tasks. Can you do a comparison of them in terms of usability, performance or learning curves of these technologies. And I'm glad to know if you have another option to suggest.
Thanks in advance,
I think you should go with signalR. It is part of .net framework, it also supports web sockets and if any client doesnt support web sockets it will fallback to long-polling, forever frames any other technology available.
.NET 4.5 WebSockets vs SignalR
http://www.asp.net/vnext/overview/signalr/signalr-and-web-sockets
http://www.hanselman.com/blog/YourUsersDontCareIfYouUseWebSockets.aspx
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
My application is built into WPF using Infragistics control(xaml).
I wanted to port the existing app into Web but we don't want to use silverlight(for silverlight we need plugin to be available in our browser and target users will not be having permission to install any plugin into their browser) is there any third part control available which helps us to port our WPF pages into WEB faster.
There are two ways to port WPF to web:
Silverlight (which you said you can't use) and
WPF XAML Browser Applications
Those are the only options I'm aware off.
If you want to convert your WPF app to ASP.NET Web forms or MVC you would have to do it manually.To make it easier you could create shared code which can be used by both WPF and the web application.
If you've followed the MVVM pattern in the WPF project that will make your job a lot easier as you can re-use the view model in MVC (with minor changes)
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
i have a general question. I want to develop a Web Application for business process modelling. The application was build using c# and WPF as Desktop Application Software and now i would like to develope it as Web Application. what technology should i choose?
I've tried to find it myself but there are many different opinions about that topic. Is there any general rule or methodology which can help me decide?
Your question is not quite constructive. You need to talk to some Architect to understand your business and the requirements to fill up the gaps of choosing a technology. It is quite vague to answer your question whether to choose ASP.NET webforms/MVC or probably a different platform than .NET to suit your needs.
On a general answer, if you are planning to port your whole application developed on desktop using WPF, you can consider porting to Silverlight which might cut down your cost to 90% (probably), where you will able to reuse all codes you have written so far. But that's totally your call and your business needs.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to write webservice on .NET (my Client can be Android, iOS, Mac OS, Website...). My question is that I should use WCF or ASP.NET to do this?
I assume you mean ASP.net Web Apis when you mention ASP.net. There is also ASP.net soap services but those won't be ideal to work with on platforms such as android or iOS.
If you are unsure about what the different web services are, you will most likely want to use ASP.net Web APIs as these are easy to set up and offer multiple content types, XML, JSON, possibly more...
WCF is more built for web services however it has a steep learning curve, which is why I say if you're unsure about what you want, you most likely aren't making something which will require WCF.
For more information I suggest reading: http://idesign.net/articles/asp_net_web_api_vs_wcf.htm
I am assuming you are asking for WCF or websevice. I think WCF is better option. For your refrence:
http://www.thedevheaven.com/2012/10/difference-between-wcf-and-web-service.html
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
This is not meant to be a subjective or argumentative question.
I am investing some time in learning ASP.NET and more specifically ASP.NET MVC and I am curious how it stacks up to the competition. I really like what I am seeing so far with the framework, and I think the icing on the cake would be if it shows rock solid speed like I have seen with some ASP.NET form sites.
Has anyone done or seen fair comparisons or benchmarks? I would be interested to see how ASP.NET MVC stacks up against other solutions such as PHP MVC too.
If you compare just raw execution .NET is faster than PHP or RoR. However, the speed and overall performance of an application depends on its architecture. For example: StackOverflow runs on less than 10 servers. I work for a company that runs a website with pretty much the same hardware (+- 10 heavy work servers) but SO is way faster and has hundred times more access that my company's website.
So in most case it is really about how you implement the software other than the platform itself.
You can not compare the language only based on speed. Each language has its own features. So you need to choose as per your requirement.
For example. If you want less spendings on hosting and other stuff then go for PHP else if you want pure MVc then gofor ruby on rails or asp.net mvc.