Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003 - Extend It! ( Programming in VS2003, ASP.Net 1.1 )

Forum General DotNetN... Extend It! ( Pr... Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

2/9/2006 2:55 AM

	Ray Brennan
50 posts

Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

Hello.
I have developed a ASP.NET (DotNetNuke 3.2) project with Visual Studio 2003 on PC1. The project folder resides in C:\thewebs\ams\. The project compiles properly on PC1. I have a IIS Virtual Directory named "ams"setup on PC1 that points to C:\thewebs\ams\. When I browse to http://localhost/ams/default.aspx I can see the compiled application as I expect to. Everything works fine here.

We want to make use of VSS2005 source safe control.

I go to PC2 and create C:\thewebs\ams\. I set the VSS working folder to here and Get Latest. All of the files are copied to this location. PC1 and PC2 have the same amount of files and folders and structure etc. Staying with PC2 I go to IIS and create a Virtual Directory named "ams" that points to C:\thewebs\ams\ and has all the same rights as the virtual directory on PC1. Both PC's are now identically setup.

This is where the headaches and they unexpected errors starts...
I browse to the solution on PC2 and open it. A dialog appears "Set Project Location". The default path given is http://localhost/ams_1/default.aspx.
If I remove the "_1" I get an error telling me that the path is invalid. If I accept this path a lot (not all) of the files are copied to
"C:\Inetpub\wwwroot\ams_1" I know have duplicate files on the PC and some of the project references are lost. When I reset the references and get it to recompile as it wants and then browse to "http://localhost/ams_1 " I get a "Parser Error"

Work around (not using VSS)
If I simply copy the working folder over the network from PC1 to PC2 and setup the virtual directory it will work no problem. So there is definately something the VSS is doing to my project files. I have used VSS with a standard windows application for testing too with apparently no problems.

If you have experiences with this and can offer any suggestions I'd love to hear from you.

Thank you.

Ray.
Dublin, Ireland.

2/13/2006 7:57 AM

	Ray Brennan
50 posts

Re: Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

Ok, putting it another way (since I'm not getting a great response)... Is anyone having problems with VSS in a multi-user environment when using DNN?

Ray.

2/13/2006 8:01 AM

	Ray Brennan
50 posts

Re: Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

Or yet another way... (give me hope)
Is anybody using VSS 2005 with DNN and Visual Studio 2003 in a multi-user environment successfully?

2/27/2006 2:03 PM

	Stefan Kamphuis
316 posts
www.superska.net

Re: Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

Hi,
To be honoust, I can't follow you all the way through your description, but maybe I can help you by describing how I'm using VSS2005 and VS.net 2003 in a team environment.

We had some issues in the beginning (the VSS6 days) with DNN included under sourcecontrol, which led to the following configuration. We're using this for about half a year now.

* On PC1, install a clean DNN.
* After the installation has finished, copy the entire directory to PC2 and make it run there too (web app in IIS, aspnet permissions...).
* Create a blank solution (CustomerName.All) under Solutions, containing a BuildSupport Project.
* Add your custom module projects to this solution and add the solution to Sourcecontrol. Notice that you will need to create references to DotNetNuke.DLL in stead of the project DotNetNuke to get it compilable.
* On PC2, set the working folder of the project containing both "Solutions" and "Desktopmodules" to your DNN directory and get the latest version (open solution from source control from within vstudio puts things in the wrong directories i think).
* At this point you should be able to open the created solution and run it (after you've set the debug action on the startup project to open the right url)

We use this solution to contain all modules and each developer (optionally) creates his own working solution. These working solutions don't get added to VSS, but all module projects do.

That about describees the way we do it. I hope it's helpful.

Greetz, Stefan Kamphuis

2/28/2006 10:16 AM

	Rob Adams
4 posts

Re: Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003

Does everyone have their own localhost DNN database in this model? We are attempting a team approach also and need advice.

Page 1 of 2

Forum

General DotNetN...

Extend It! ( Pr...

Help please - VSS2005 sharing ASP.NET / DNN3.2 Project - Visual Studio 2003