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.
Related
I have written a website in Visual Studio using .Net Framework (4.7.2). (Note: it is not using .net Core)
It is an asp.net website that uses .aspx pages and uses a SQL Server Database on my laptop.
Is it possible to run this website on my Synology NAS and if so would it be able to connect to the database on my laptop (that is on the same network).
.Net framework app can only be run in Windows OS. But Synology is Linux based.
So if you want to run your app in Synology badly, you need to convert it to .Net Core app.
Here is my answer in another question explaining how to run .Net core app in Synology.
Publish Net Core Web API in NAS Synology
You need a full os running windows, and then you also need sql server installed, and you also need iis (internet services (the web server)) installed on that server.
So you need a windows os, and preferably a server based version of windows (such as windows server 2019).
Unless that server allows you to install and run windows software? Then no that will not work.
Consider more than 2 .net applications running in IIS Server, They may be running on either Targeted .NET framework Version (If It is available in Server Machine) or later .net Version. Is there any way to Get the .NET version of Each app running on the IIS Server in a single shot
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 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.
I have XP pro edition with .Net 3.5 installed and IIS 5.0 and MVC RC 2
Can i run KiGG on this machine?
Also i have on my hosting server IIS 6 and .Net 3.5 , can it run there or no also?
If no, there is no work around to make it work?
Thanks,
You would need to install an SQL server but yes, you can run KIGG on IIS 5/XP.
ASP.NET MVC is bin-deployable so you should be able to run it on your host also. I think for a shared host you'll need full trust because it uses some reflection in the code, otherwise you'll get exceptions.