Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Oct 28, 2009 02:11 PM by yaip
Oct 23, 2009 10:27 PM|LINK
Can I run an ASP.NET application on a Windows 2000 machine that has no internet connection? If yes, what do I need on the machine? If I have to create a "deployment CD" what all does it need to have?
Oct 24, 2009 01:38 PM|LINK
ASP.NET 3.5 is not compatible with Windows 2000, so this would not be possible.
ASP.NET 2.0 can run on Windows 2000 as long as Service Pack 4 is installed. Given this, you need to install the .NET Framework 2.0 on this computer which you would include in your "deployment" CD. You will also need to make sure that IIS is installed and
that you are using the Microsoft Loopback Adapter to simulate connectivity with your "web" environment. As for the application, you should be able to copy the files and then configure IIS for your website.
Note that unless you are using a DNS server on your Windows 2000 box, then you can only use the Default Website for your application since you will not have DNS functionality. This is, of course, only applies if you're using the 2000 Server. If you're
using W2K Professional, then you can only have one website (Default) anyway.
I've probably left something out, but this should get you started.
One question: When you say "no internet connection", do you mean that it is networked, but has no connection to the Internet, or that it has no network connectivity at all? This could change how you would set up the machine.
Oct 24, 2009 04:03 PM|LINK
So silverlight 3 is out? I was thinking of taking advantage of it's OOB functionality. It will be W2K Professional. Won't IIS be automatically installed? I am not too sure if it will be a stand-alone PC or a networked PC. Is there an advantage if it is networked?
Oct 24, 2009 04:30 PM|LINK
Does this mean LINQ also is out?
Oct 26, 2009 01:37 PM|LINK
Silverlight 3 requires a minimum of Windows XP Pro SP2, so it is out of W2K Pro. LINQ is also out as it is officially part of .NET 3.5.
As for IIS, if you perform a typical installation, it may not have been installed because it's not considered a server. You should be able to check and see if you have the IIS Manager within the Administrative Tools under the Control Panel.
The advantage of being networked is that you can use the network to copy files back and forth. This way, you will not need to make CDs to transfer your files around. Then again, you might be able to use USB drives, but there could be some compatibility
issues with the latest versions. At the very least, with a network share, you could have all of your installation programs and files available for copying across. However, since you will installing some of this software without Internet access, you may need
to use some of the ISO files since you'll need to do standalone installations. Though, you could expand the files from an ISO file and place them on a network share for installation.
Oct 26, 2009 04:02 PM|LINK
The application will be installed on various locations. So I have no way of knowing what the infrastructure is going to be. All I have to know is that a CD drive will be there and the target OS will be W2K Pro. So I've to pack everything on the CD (including
any Framework or runtime that is needed). Is there anything like InstallShield available that is free?
Oct 26, 2009 04:34 PM|LINK
So, this begs the question as to why is Windows 2000 Pro still in use. It is a retired OS with no current support, so why need upgrade at least to Windows XP Pro with the latest service pack?
Oct 26, 2009 04:47 PM|LINK
That was my very first question :)
But I am not in a position to decide what OS the client's machine has. I just know that I've to develop a solution with the following requirements/restrictions:
- Target OS is W2K.
- No Internet access.
- Don't know is the PC is networked.
- Intall to be done via a CD.
Oct 27, 2009 05:12 AM|LINK
Then, you will need to .NET Redistributable for version 2.0 and then a ZIP file of your code. You could try to use an installer, but you will need a professional version to get the .NET installed before installing your code/application. You should be able
to get everything on a CD.
If you copy the code over, you could use a batch file (.CMD) to run the redistributable and then copy to files over to a directory of your own creation.
Oct 28, 2009 01:54 PM|LINK
I've to develop a solution with the following requirements/restrictions:
Then you have to live in those restrictions. No ASP.NET 3.5 functionality. And what's even stranger, no way to access the web app from off the system anyway, so basically useless to develop.
Are you sure you don't need a Windows app isntead of a web app? A Windows app isn't ASP.NET, it's C#.NET or VB.NET, and there are appropriate forums for them on other sites.