Let's say what I did:
After running DNN 4.03 for a while I decided to make some modifications. - On module level, this works fine by using VWD within the /Website folder (I installed source package 4.03 and used this folder according to the self-compiling features of ASP.NET).
Now, I have to do some minor mods to DNN itself (especially the Help.vb), so I have to to do new builds, and for, uhm, good reasons I decided to make a fresh install of the whole source 4.03 package to build a new /bin and copy it carefully to the already modified, running DNN application site (so is my plan, btw is it ok...?).
Well, I created a new file share on my (local) server, set up rights for ASP.NET, unzipped the 4.03 source package to the known /Library, /Website, DotNetNuke.sln structure and created a new virtual dir named DotNetNuke_2 pointing to that share with the appropriate settings for a normal DNN install. - Then I set up a new database with the rights for my standard user (SQL auth). - Last I renamed develop.config (!) to web.config and changed the connection string to the new db.
DNN Setup ran fine, a typical 4.03 without errors. I logged in and felt at home. -
Next, I created a new virtual dir named "clone" pointing to <share>/Website to do DNN configs, f.e. setting up a new http alias, as I'm working on the server to do install jobs, but I like to do testing from other machines, too. - So, my poor standard DNN is up and running on http://artagens.dynaccess.de/clone at the moment. - have a look, if you like.
Rubbing my hands, I ran Visual Studio 2005 on the server (local), checked all for the last time, opened DotNetNuke.sln on the file share as above (c:\inetpub\wwwroot\... being DotNetNuke_2 virtual dir) and... and... as expected after some painful months with .NET... it doesn't run. NO. What a great result. I'm perfectly amused!
- Same errors as I always had, "The application for project 'http://localhost/DotNetNuke_2' isn't installed. Ensure that the application is installed for project type ()." followed by various errors that name the correct (!) local paths of the .vbproj files and the correct project types (.vbproj). -
Now I feel myself on the end of a path... what else could be wrong? Is there a chance to get off Visual studio and do a manual build or assembly? Remember, I just wanted to change 8 lines in help.vb...!?
Any idea, can you help me? Thanks, itagens