Search:   Namespaces Discussions .NET v1.1 Feedback

Setting multiple "root web" projects Messages   Related Types This message was discovered on ASPFriends.com 'aspngvs' list. Michael Wells I am searching for the "correct" way to setup projects in VS.NET, so that I can switch between several "root web" projects. My team generally works on 3-4 projects simultaneously, and none of them will run in virtual directories. At the same time, I'm looking to formally configure DEV/TEST/PROD environments ( VS.NET only needs to be aware of DEV ), and to ensure that debugging is fully operational. I've run into several issues in setting this up, and I think (hope?) that I may be overcomplicating my approach to creating a basic development environment. Here's what I've done/learned so far... ( corrections / recommendations are much appreciated ). Because my development systems use 2000 workstation, I am unable to create more than one website in IIS. The Internet Services Manager does not permit this ( and I've verified that this is the intended behavior, even when multiple IPs have been assigned to the system ). I'm not interested in using virtual directories, for several reasons. Most notably, I find it inconvenient (and error prone) to require the team to use relative paths across the board. It's important to me that anything they build on http://devbox/project will deploy smoothly to http://testbox (no virtual dir) without modification. So, I have set up a development server to house the projects, assigned roughly 50 internal IP's and created symbolic names in my development system's HOSTS file... 10.100.0.1    project1.dev 10.100.100.1    project1.test 10.100.0.2    anotherproject.dev 10.100.100.2    anotherproject.test 10.100.0.3    yetanotherproject.dev 10.100.100.3    yetanotherproject.test It seems that VS should automate this in some way, but I haven't come across any docs on how to do this. Using the above approach, I am able to create web projects successfully, but a little bit of manual cleanup is required... + I have to fully re-define the project path. VS.NET doesn't like to deal with "http://project1.dev"; as a project location, but with some handholding, it works. + Once the project is created, I have to change the namespace and remove ".dev" (since the project itself will traverse DEV/TEST/PROD). A little manual editing of the VS.NET source files is also required. + If the project existed elsewhere, I have to manually add those files to the new project, changing namespaces as necessary. Generally, this allows me to get the project created on a remote server, and make it accessible. With VSS, I can prevent developers from overwriting each other's work. PROBLEMS... #1... this approach seems much less elegant than it should be, which suggests to me that I'm missing some important feature or generally-accepted-configuration for this. #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). #3... I've had tremendous difficulty getting debugging to work. I have installed remote debugging support, and added all developers to the "Debugging Users" (?) group, but I still receive an "Access Denied" when I try to attach to the aspnet_wp.exe process. ( our projects are mostly ASP.NET ). Advice is much appreciated. -- Michael Wells=20 Reply to this message...        Stefan Walther The best way solving the problems mentioned below is a combination of host-headers in IIS, if you also like to offer your webs for external access (but you only have one external IP-address, use the same webs but with ports); We have changed all customer-webs one year ago and we are really happy with this solution ... greetings Stefan ----- Original Message ----- From: "Michael Wells" <Click here to reveal e-mail address> To: "aspngvs" <Click here to reveal e-mail address> Sent: Wednesday, July 10, 2002 2:04 AM Subject: [aspngvs] Setting multiple "root web" projects I am searching for the "correct" way to setup projects in VS.NET, so that I can switch between several "root web" projects. My team generally works on 3-4 projects simultaneously, and none of them will run in virtual directories. At the same time, I'm looking to formally configure DEV/TEST/PROD environments ( VS.NET only needs to be aware of DEV ), and to ensure that debugging is fully operational. I've run into several issues in setting this up, and I think (hope?) that I may be overcomplicating my approach to creating a basic development environment. Here's what I've done/learned so far... ( corrections / recommendations are much appreciated ). Because my development systems use 2000 workstation, I am unable to create more than one website in IIS. The Internet Services Manager does not permit this ( and I've verified that this is the intended behavior, even when multiple IPs have been assigned to the system ). I'm not interested in using virtual directories, for several reasons. Most notably, I find it inconvenient (and error prone) to require the team to use relative paths across the board. It's important to me that anything they build on http://devbox/project will deploy smoothly to http://testbox (no virtual dir) without modification. So, I have set up a development server to house the projects, assigned roughly 50 internal IP's and created symbolic names in my development system's HOSTS file... 10.100.0.1 project1.dev 10.100.100.1 project1.test 10.100.0.2 anotherproject.dev 10.100.100.2 anotherproject.test 10.100.0.3 yetanotherproject.dev 10.100.100.3 yetanotherproject.test It seems that VS should automate this in some way, but I haven't come across any docs on how to do this. Using the above approach, I am able to create web projects successfully, but a little bit of manual cleanup is required... + I have to fully re-define the project path. VS.NET doesn't like to deal with "http://project1.dev"; as a project location, but with some handholding, it works. + Once the project is created, I have to change the namespace and remove ".dev" (since the project itself will traverse DEV/TEST/PROD). A little manual editing of the VS.NET source files is also required. + If the project existed elsewhere, I have to manually add those files to the new project, changing namespaces as necessary. Generally, this allows me to get the project created on a remote server, and make it accessible. With VSS, I can prevent developers from overwriting each other's work. PROBLEMS... #1... this approach seems much less elegant than it should be, which suggests to me that I'm missing some important feature or generally-accepted-configuration for this. #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). #3... I've had tremendous difficulty getting debugging to work. I have installed remote debugging support, and added all developers to the "Debugging Users" (?) group, but I still receive an "Access Denied" when I try to attach to the aspnet_wp.exe process. ( our projects are mostly ASP.NET ). Advice is much appreciated. -- Michael Wells | [aspngvs] member Click here to reveal e-mail address = YOUR ID | http://www.asplists.com/asplists/aspngvs.asp = JOIN/QUIT | http://www.asplists.com/search = SEARCH Archives Reply to this message...        Omar Khan With regards to this issue:     #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). It is a known bug and we are looking at addressing it in an upcoming service release. Omar Khan Visual Studio .NET -----Original Message----- From: Stefan Walther [mailto:Click here to reveal e-mail address]=20 Sent: Wednesday, July 10, 2002 8:35 AM To: aspngvs Subject: [aspngvs] Re: Setting multiple "root web" projects The best way solving the problems mentioned below is a combination of host-headers in IIS, if you also like to offer your webs for external access (but you only have one external IP-address, use the same webs but with ports); We have changed all customer-webs one year ago and we are really happy with this solution ... greetings Stefan ----- Original Message -----=20 From: "Michael Wells" <Click here to reveal e-mail address> To: "aspngvs" <Click here to reveal e-mail address> Sent: Wednesday, July 10, 2002 2:04 AM Subject: [aspngvs] Setting multiple "root web" projects I am searching for the "correct" way to setup projects in VS.NET, so that I can switch between several "root web" projects. My team generally works on 3-4 projects simultaneously, and none of them will run in virtual directories. At the same time, I'm looking to formally configure DEV/TEST/PROD environments ( VS.NET only needs to be aware of DEV ), and to ensure that debugging is fully operational. I've run into several issues in setting this up, and I think (hope?) that I may be overcomplicating my approach to creating a basic development environment. Here's what I've done/learned so far... ( corrections / recommendations are much appreciated ). Because my development systems use 2000 workstation, I am unable to create more than one website in IIS. The Internet Services Manager does not permit this ( and I've verified that this is the intended behavior, even when multiple IPs have been assigned to the system ). I'm not interested in using virtual directories, for several reasons. Most notably, I find it inconvenient (and error prone) to require the team to use relative paths across the board. It's important to me that anything they build on http://devbox/project will deploy smoothly to http://testbox (no virtual dir) without modification. So, I have set up a development server to house the projects, assigned roughly 50 internal IP's and created symbolic names in my development system's HOSTS file... 10.100.0.1 project1.dev 10.100.100.1 project1.test 10.100.0.2 anotherproject.dev 10.100.100.2 anotherproject.test 10.100.0.3 yetanotherproject.dev 10.100.100.3 yetanotherproject.test It seems that VS should automate this in some way, but I haven't come across any docs on how to do this. Using the above approach, I am able to create web projects successfully, but a little bit of manual cleanup is required... + I have to fully re-define the project path. VS.NET doesn't like to deal with "http://project1.dev"; as a project location, but with some handholding, it works. + Once the project is created, I have to change the namespace and remove ".dev" (since the project itself will traverse DEV/TEST/PROD). A little manual editing of the VS.NET source files is also required. + If the project existed elsewhere, I have to manually add those files to the new project, changing namespaces as necessary. Generally, this allows me to get the project created on a remote server, and make it accessible. With VSS, I can prevent developers from overwriting each other's work. PROBLEMS... #1... this approach seems much less elegant than it should be, which suggests to me that I'm missing some important feature or generally-accepted-configuration for this. #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). #3... I've had tremendous difficulty getting debugging to work. I have installed remote debugging support, and added all developers to the "Debugging Users" (?) group, but I still receive an "Access Denied" when I try to attach to the aspnet_wp.exe process. ( our projects are mostly ASP.NET ). Advice is much appreciated. -- Michael Wells=20 | [aspngvs] member Click here to reveal e-mail address =3D YOUR ID | http://www.asplists.com/asplists/aspngvs.asp =3D JOIN/QUIT | http://www.asplists.com/search =3D SEARCH Archives | [aspngvs] member Click here to reveal e-mail address =3D YOUR ID | http://www.asplists.com/asplists/aspngvs.asp =3D JOIN/QUIT | http://www.asplists.com/search =3D SEARCH Archives Reply to this message...        Goldfarb, Christopher Omar, Are there any general ideas as to when the service pack will be available? There are a couple issues which I can't wait to get fixed (property window locking, winform debug hanging, and webform reformatting, to name a few). Chris -----Original Message----- From: Omar Khan [mailto:Click here to reveal e-mail address] Sent: Wednesday, July 10, 2002 10:28 AM To: aspngvs Subject: [aspngvs] Re: Setting multiple "root web" projects With regards to this issue:     #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). It is a known bug and we are looking at addressing it in an upcoming service release. Omar Khan Visual Studio .NET -----Original Message----- From: Stefan Walther [mailto:Click here to reveal e-mail address] Sent: Wednesday, July 10, 2002 8:35 AM To: aspngvs Subject: [aspngvs] Re: Setting multiple "root web" projects The best way solving the problems mentioned below is a combination of host-headers in IIS, if you also like to offer your webs for external access (but you only have one external IP-address, use the same webs but with ports); We have changed all customer-webs one year ago and we are really happy with this solution ... greetings Stefan ----- Original Message ----- From: "Michael Wells" <Click here to reveal e-mail address> To: "aspngvs" <Click here to reveal e-mail address> Sent: Wednesday, July 10, 2002 2:04 AM Subject: [aspngvs] Setting multiple "root web" projects I am searching for the "correct" way to setup projects in VS.NET, so that I can switch between several "root web" projects. My team generally works on 3-4 projects simultaneously, and none of them will run in virtual directories. At the same time, I'm looking to formally configure DEV/TEST/PROD environments ( VS.NET only needs to be aware of DEV ), and to ensure that debugging is fully operational. I've run into several issues in setting this up, and I think (hope?) that I may be overcomplicating my approach to creating a basic development environment. Here's what I've done/learned so far... ( corrections / recommendations are much appreciated ). Because my development systems use 2000 workstation, I am unable to create more than one website in IIS. The Internet Services Manager does not permit this ( and I've verified that this is the intended behavior, even when multiple IPs have been assigned to the system ). I'm not interested in using virtual directories, for several reasons. Most notably, I find it inconvenient (and error prone) to require the team to use relative paths across the board. It's important to me that anything they build on http://devbox/project will deploy smoothly to http://testbox (no virtual dir) without modification. So, I have set up a development server to house the projects, assigned roughly 50 internal IP's and created symbolic names in my development system's HOSTS file... 10.100.0.1 project1.dev 10.100.100.1 project1.test 10.100.0.2 anotherproject.dev 10.100.100.2 anotherproject.test 10.100.0.3 yetanotherproject.dev 10.100.100.3 yetanotherproject.test It seems that VS should automate this in some way, but I haven't come across any docs on how to do this. Using the above approach, I am able to create web projects successfully, but a little bit of manual cleanup is required... + I have to fully re-define the project path. VS.NET doesn't like to deal with "http://project1.dev"; as a project location, but with some handholding, it works. + Once the project is created, I have to change the namespace and remove ".dev" (since the project itself will traverse DEV/TEST/PROD). A little manual editing of the VS.NET source files is also required. + If the project existed elsewhere, I have to manually add those files to the new project, changing namespaces as necessary. Generally, this allows me to get the project created on a remote server, and make it accessible. With VSS, I can prevent developers from overwriting each other's work. PROBLEMS... #1... this approach seems much less elegant than it should be, which suggests to me that I'm missing some important feature or generally-accepted-configuration for this. #2... when building projects, I find that the DLLs in the BIN directory often become locked. I know that this isn't supposed to happen; but I'm not familiar with the internals of the "shadowing" process and what might cause it to break. This creates severe problems, since the development server has to be rebooted to unlock those files ( restarting the webserver doesn't help ). #3... I've had tremendous difficulty getting debugging to work. I have installed remote debugging support, and added all developers to the "Debugging Users" (?) group, but I still receive an "Access Denied" when I try to attach to the aspnet_wp.exe process. ( our projects are mostly ASP.NET ). Advice is much appreciated. -- Michael Wells | [aspngvs] member Click here to reveal e-mail address = YOUR ID | http://www.asplists.com/asplists/aspngvs.asp = JOIN/QUIT | http://www.asplists.com/search = SEARCH Archives | [aspngvs] member Click here to reveal e-mail address = YOUR ID | http://www.asplists.com/asplists/aspngvs.asp = JOIN/QUIT | http://www.asplists.com/search = SEARCH Archives | [aspngvs] member Click here to reveal e-mail address = YOUR ID | http://www.asplists.com/asplists/aspngvs.asp = JOIN/QUIT | http://www.asplists.com/search = SEARCH Archives Reply to this message...        Michael Wells Thanks Omar, is there a specific approach I can take to avoid this problem in the short term? What scenario causes the issue? -- Michael Wells [Original message clipped] Reply to this message...        Michael Wells Hi Stefan, We do use host headers for PROD sites (except https: sites), but we are not currently using them for TEST or DEV sites. =20 Thanks for the advice; I'll definately give that approach a try. =20 -- Michael Wells Managing Consultant Practical Design Group 312.922.7991 [Original message clipped] Reply to this message...        Omar Khan Until a fix is available, the workaround you mention below is all that you can do. I'm looking into the availability of a fix, and I'll get back to you on what I find out. Omar Khan Program Manager Visual Studio .NET -----Original Message----- From: Michael Wells [mailto:Click here to reveal e-mail address]=20 Sent: Wednesday, July 10, 2002 11:35 AM To: aspngvs Subject: [aspngvs] Re: Setting multiple "root web" projects Thanks Omar, is there a specific approach I can take to avoid this problem in the short term? What scenario causes the issue? -- Michael Wells [Original message clipped] | [aspngvs] member Click here to reveal e-mail address =3D YOUR ID | http://www.asplists.com/asplists/aspngvs.asp =3D JOIN/QUIT | http://www.asplists.com/search =3D SEARCH Archives Reply to this message...     Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com