I have developed an MVC 3 (using .NET 4.0 and not .NET 3.5 SP1) application with jQuery Mobile that communicates with a legacy application's business layer built in 3.5. Now the time has come to upload the application to a production server. However issues have arised. Namely, the client insists that the mvc app should be a sub app of a desktop version of the same app (built in 3.5). What do I do now?
You could use IIS Express to host the web application locally. IIS Express can be packaged within an application installer and distributed to the users.
The desktop app can then have a simplified browser window that navigates to the local web application.
... an ugly solution to a problem that shouldn't exist.
Related
I'm developing a web MVC app using .NET Framework 4.7
Since two days, I can't access to my app in the browser. It runs in Visual Studio 2019 but not in the browser. I have a 404. I think the problem is from my computer because my mates can run my app on their own computer. Maybe it's a problem with IIS but I don't know how to fix this.
I can find similar questions, but those answer is not clear or no answer (all answered now) that make me confuse .
Similar questions 1
Similar questions 2
Now Visual Studio has 3 Web Project template :
ASP.NET Web Application (.NET Framework) <-- old
ASP.NET Core Web Application (.NET Core) <-- new
ASP.NET Core Web Application (.NET Framework) <-- new
I know the different between .NET Core and .NET Framework.
.Net Core - can cross platform(Windows, OS X, Linux)
.NET Framework - Windows Only
Then, the problem:
If we can use .Net Core in cross platform include Windows,
Why there still need ASP.NET Core Web Application(.NET Framework)(new) ?
If only work on Windows ,
Why don't just use ASP.NET Web Application (.NET Framework)(old)? which much mature and more support.
What is the purpose/usage of ASP.NET Core Web Application (.NET Framework)(new)??
.NET Core does not have all the APIs available in .NET Framework. As a result when running on Windows you may want to target full .NET Framework instead of .NET Core in your Asp.NET Core application.
Asp.NET 4.x is still supported and it's perfectly fine to create new applications using Asp.NET 4.x.
However, the vast majority of innovation goes to Asp.NET Core. Asp.NET Core is also open source so you can actually see the code you are running, debug the code you are running and even contribute back your fixes or new features. Finally, Asp.NET Core is also much more lightweight (everything is a NuGet package and you only include what you need, not coupled to IIS - runs out-of-proces when using IIS) and much faster than ASP.NET.
I am using Visual Studio 2012. I have been developing on a legacy web site that uses .NET 2.0. It is configured on my local machine using IIS with an application pool set for .NET 2.0. I am able to open this web site from Visual Studio using File-Open-Web Site....no problem. This is a web site, not a compiled web application.
I just changed my application pool to .NET 4.0. My web site runs fine.
However, when I select File-Open-Web Site in Visual Studio, I get an error that says:
The site "...." is currently configured for use with a newer version of ASP.NET (4.0). This project is targeting ASP.NET 2.0; if not configured some features with the tool may not render correctly. Would you like the site to be configured for user with ASP.NET 2.0?
I can click "No" and attach to and debug the application no problem.
I have no SLN, SUO, CSPROJ, or USER files anywhere in the web site or in My Documents. I have deleted the contents of my web.config file so that it is empty. I still continue to get this message every time I open the web site.
Where is this message coming from?
Why does Visual Studio think that the web site is configured for .NET 2.0?
This is something local to my machine.
Other developers in the company have upgraded their application pool to 4.0 and do not see this message when opening the web site from Visual Studio.
While you may have upgraded your solution to be opened by Visual Studio 2012, you haven't changed the targeted .NET runtime.
To target something other then the .NET 2.0 runtime you need to change the target in the project properties.
See the following for a complete explanation.
I have a query while hosting my web application in IIS:
* whether we need .net framework to be installed in the hosting machine with IIS?
SHort answer - yes, you need the .NET Framework installed. A .NET application won't run without the Framework.
You'll also want to make sure you set the correct framework for the web application under the ASP.NET tab, depending on what version the application was written in.
Yes, as the .NET framework is what allows a .NET application to be utilized. Here is a complete guide from Microsoft: http://msdn.microsoft.com/en-us/library/ms178477.aspx
Can the IIS version in Windows Server 2008 R2 host all the following:
SharePoint 2010;
ASP.Net 4.0;
Classic ASP applications;
VB6 compiled .dll web applications.
If so, can SharePoint 2010 be the Default Web application when accessing the server?
Thanks,
Aaron
Sharepoint 2010 requires the .Net 3.5 framework.
I guess it's because a new SP version was being developed at the same time as the new .Net version, SP 2010 couldn't use .Net 4.0 yet.
Edit: here's the explanation in the words of the SharePoint Product Manager:
Unfortunately the release timeframes
didn't work out to get SharePoint 2010
built on .NET Framework 4.0.
I'm not sure about VB6 compiled .dll web application, but the rest is no problem.
Classic ASP isn't installed by default, but it's just a feature to enable.
As SharePoint is running .Net 3.5 it needs to be in a seperate AppPool from your .Net 4.0 sites.
Which site is the default is just a matter of selecting which Web Site is serving port 80 without a host header.
The separation; that needs to be explained here is the "application pool" term; a pool can use only one .net version so if they're in different application pools then everything is fine for IIS.
With the default web application is a relative object; if you mean through http://example.com then this means the port 80 is assigned to eg. Sharepoint on the application server.