Don't want to install IIS locally- how are your development environments set up?
-
Hey all, I'm just getting into VS.NET and ASP.NET and etc. I previously used classic ASP and a text editor (I have InterDev 6.0 but never used it), so I'm just wondering how you've set up your VS.NET development environments. The VS.NET IDE makes much more sense to me then that InterDev junk, but I'm not sure how to set up my computer with it, because: I don't want to install IIS locally on my machine! My development environment with Visual Studio 6.0 and ASP stuff was: 1. Development PC, Win2000 Pro, VS 6.0 2. Test server, Win2k advanced server, IIS 5.0 3. Production server, Win2k advanced server, IIS 5.0 ** ALL machines are "mirrors" of patches/MDAC versions/updates/software versions/etc Right now I've got VS.NET on my XP-Pro laptop with IIS 5.1 running. It's on my notebook because I don't want to change my development PC. For example, all three computers above have Win2k SP 3 with MDAC 2.5 (not SP4 with MDAC 2.7). I'm "learning" the VS.NET suite, so this one-computer environment works for me- for now. But here's where I get concerned about the setup of test servers and production servers and not running IIS locally: When I create a new C# "ASP.NET Web Application", I tell VS to put it on http://localhost/myapp . That's all great for now since I'm using my laptop, and, of course, have full rights/access to the hard drive. (When I use VS.NET, I log in as administrator to XP-Pro, and pull the ethernet cable out.) How would I create a "ASP.NET Web Application" in the above 3-system development environment? Would I tell it to use http://mytestserver/myapp ? Or would i have to use the FQDN, such as http://mytestserver.mycompany.org/myapp ? Would I just need to share the D:\inetpub\wwwroot folder out in my test server's AD? Or do I have to put read/write/everything privleges on the virtual directory inside the test server's IIS snap-in? Do I need to add additional shares to the test server... such as, does VS.NET try to put anything in the C:\WINNT directory? I'll need to install "Frontpage extensions" on the test server, right? Also, how in the world would I move changes to my production server? Would I just copy over the files that have changed? Or do I need to copy the whole directory to the production server? Is there some kind of deployment wizard that would take care of this? Do I need FrontPage Extensions on my production server?? I'd rather not install those; I prefer to keep extra crud off the production systems. I used to just develop ASP.NET pages in TextPad