I have been playing around deploying my .NET Core application on several Operating Systems using self-contained and portable platforms.
As expected, this runs fine on Windows 8.1, Windows 10 and OSX.
I also have a 2008 Windows Server with IIS7 and this is causing a few issues. I have tried to run the self-contained executable but returns procedure entry point kernel32.dll error which apparently means that I have selected the wrong runtime in my project.json file.
Where can I get a list of compatible ASP.NET Core runtimes?
I believe portable .NET Core apps are NOT compatible with IIS7 as AspNetCoreModules requires IIS7.5, is this correct?
The article Publishing to IIS on ASP.NET Core docs says that Windows Server 2008 R2 is required.
Related
Plain and simple: Is it even possible for a SignalR Application to run off IIS 8.5 on Windows Server 2012 R2, or is this not a compatible setup? There are tons of threads all over Stack Overflow that pose the same issue, that the dynamically generated script located at signalr/hubs is 404ing, but the threads with solutions are not using my iis/server setup.
I tried following the tutorial at https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/tutorial-getting-started-with-signalr but it seems that it only works in Visual Studio's IIS Express. As soon as I move the application to our server, I get the error everyone else on SO is getting.
Here's the supported platforms for Signalr on the official documentation:
https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/supported-platforms
It stops short of Windows Server 2012 R2, but the documentation is dated. Any advice is appreciated.
Yes, Windows Server 2012 R2 and Windows Server 2016 both support SignalR. Just ensure WebSocket support is enabled and you're all set.
IIS Express is a cut-down version of IIS (which frustratingly does not work with IIS Manager), but internally it uses the same execution engine (including HTTP.sys integration) so it uses the same web.config files as the full-fat IIS too, so it supports SignalR too.
("IIS Express" is a thing because previously VS shipped with a simple web-server called Cassini, which used ASP.NET System.Web.dll for everything, which worked for simple applications but for more complex applications there was sufficient differing behaviour that it made development difficult)
I have developed an asp.net web application in Visual Studio 2008
with dotnet framework 2.
I hosted this application.
I tried to run this application on client machine(through browser)
which has windows 8, but my application failed to run.
Things i did to resolve the above issue:
On my client machine i installed dotnet framework 2.0, my application started
working.
But as this is not a genuine soltion as i cant install the framework on all the client machines.
Now, again I uninstalled the dotnet framework 2.0 from the same machine, the application
was still working fine(running through the browser)
If assume that some depandant files are not uninstalled by the Operating system itself.
Then i upgraded my application to framework 4.5. Still i found that application is not working
on windows 8.
So is there still some dependancy on framework 2.0?
do i need to add some additional dlls when i host the application so that it runs on
windows 8 without any dependancy on the system configuration?
Do i need to make any specific changes in the web.config?
Also note that, on the same client machine which as windows 8, i installed Visual Studio 2013,
have source code there, and when i run the same application through visual studio runtime,
my application runs just fine.
I'm reporting this error when I try to execute in debug the application:
The application you are trying to debug uses a version of the Microsoft .NET Framework that is not supported by the debugger.
The debugger has made an incorrect assumption about the Microsoft .NET Framework version your application is going to use.
The Microsoft .NET Framework version specified by you for debugging is incorrect.
I'm using Visual Studio 2008 and .NET Framework 3.5.
I've got this problem with a particular project. Another project with the same framework and visual studio version works perfectly.
This suggests me that this is a problem of the project.
Any idea of why? Which property to set?
Thank you very much
Check to ensure that the application pool you are running the site under is set for the correct .Net runtime version. In IIS you can set that up in IIS Manager site configuration. With IISExpress you just need to modify the applicationhost.config file to set the site to use the correct app pool, or configure the app pool to use the proper version.
I have an asp.net 3.5 solution developed on a 32-bit machine under VS2008, everything was working ok until it got migrated to a 64-bit machine, on Win7 Professional. The project has 32-bit third party dlls as well, but they are working fine on a 64-bit Windows 2008 Server. Then when trying to debug the application using VS2008 I get this error message:
Unable to start debugging on the web server. Mixed mode debugging is not supported on Windows 64-bit platforms.
Which I don't really understand since I thought the CLR was processor agnostic, anyway what would be my options now? I have read about upgrading to .net 4.0, debugging from IIS, running on VS2010, CasiniDev, etc. The project was working fine and I only need a quick work around for this.
CLR is processor agnostic it get converted to the correct version at run time; but the VS debugging plugins are not.
The 32bit/64bit-ness of the platform and what you're debugging has to match. If I remember correctly the bit-ness of the machine you're debugging from has to match too.
As it's a web application this may allow you to work around it.
What are the steps for deploying the .Net Web Application on Linux & apache web server developed using .NET Framework using Visual Studio 2005?
Make sure you compiled/developed for .NET 2.0 (otherwise mono might complain)
Install mod_mono
Put the files on the linux server, they should run immedatly
See how slow it runs and buy a windows server
IMHO .NET Applications on Linux still have a long way to go until they are really useable.