Archive
Monthly
Go
|
|
DNN Blog
Nov
20
Posted by:
Charles Nurse
11/20/2007
I have been working with Web Application projects for about a year now and when I developed the new Authentication providers I created them as Web Application Projects. I have also been using Visual Studio 2008 for a few months (since Beta 2 was released).
With the release of the RTM version yesterday, I downloaded the iso from MSDN and this morning I installed it on my Development Virtual Machine - (I use VmWare Workstation but thats another story for another day).
Once I had Visual Studio installed, I went to open my working solution file (I had already upgraded the core solution and projects when using the Beta 2 release). Imagine my surprise then, when I got an error message (see below):
My initial response was that maybe my Virtual Directory was not configured, but when I opened IIS Manager it was there. If I selected "Yes" then Visual Studio would attempt to create the virtual directory - but would fail as it already existed. Selecting "No" would stop the project from loading.
I did manage to load the project eventually by deleting the Virtual Directory in IIS, and then selecting the "Yes" option. The problem was that the "Web" properties were not set correctly. In previous versions of the Web Application Project implementations (VS2005 with the add-in or VS2008 Beta 2), this did not seem to matter. (Note: It could also be because I had elected to build my new Virtual Machine using Vista Ultimate Edition (with IIS7) rather than Windows Server 2003 (with IIS6).
Anyway, here are the settings for the project file:
The Project Url is the problem. In my initial set-up it had been my understanding that this should point to the root of the website. This is not quite true, and since I never used F5 or Ctrl-F5 to launch the website I never realised this. The Project URL should actually point to the relative URL for the Project (including the DesktopModules/ etc). The "Override application root URL" option is used to point at the application root (if different from the project root).
So, the correct settings should be:
Note - in addition I have configured the "Start Page", so that the Application launches the start page of the site when the user clicks F5 or Ctrl-F5.
Again, I am not sure if this more rigid behaviour is due to the RTM or the fact that I am using IIS7, but as we are likely to be using this combination more-and-more as we move forward, it is good to get it right.
9 comment(s) so far...
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
ohh you mean in WAP project, the Project URL should be something like "http://localhost/dotnetnuke/desktopmodules/myCustomModule" and the Override Application root URL should be something like "http://localhost/dotnetnuke", right ?
By IndianGuru on
11/20/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
Yes
By cnurse on
11/20/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
I thought I read somewhere that you could create multiple websites on vista ultimate. In this case you could create websites like www.DNNDev1.com etc. Is this true?
Is there a good reason to use the http://locahost... with virtual directories instead?
By pspeth on
11/21/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
One more question,
Are you running the 64bit version of Windows Vista Ultimate?
I have been debating on which version to install at home.
I have an HP that is 64bit dual core with 4Gig of RAM.
Any suggestions regarding 32 or 64?
By pspeth on
11/21/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
pspeth - Sorry I can give no advice on either question - I have just started using Vista as a development environment - I used the 32 bit version.
By cnurse on
11/21/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
@Pspeth - You can create multiple sites in Vista, however, you still need to be able to "resolve" the domain name, so you would need to create entries in your hosts file. As this is an extra step (and a manual one at that) and not one that everyone is aware of, it is probably best to stick with the current method until we have a better solution. Also, I have heard good things about 64 bit vista, however it depends on the hardware peripherals you wish to use, since many drivers are still missing for 64bit Vista.
By jbrinkman on
11/21/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
See my post here on how to "Using IIS Admin.Net with DNN" located at http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1047/Default.aspx. The process is similar for setting up a new site in Vista (Although it does not cover actually creating a new site in Vista. I might try to put together a blog on this in the near future.
By smehaffie on
11/25/2007
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
Just in case noone knows it, it isn't a Vista thing. It seems to be a VS2008 thing. I am developing on XP with IIS6 and it gave me the same errors. Thank you for posting this I would have been lost!
By coreythompson on
5/21/2008
|
Re: DotNetNuke, Web Application Projects and Visual Studio 2008
I want to set up my Visual Web Studio 2008 Express to work with my dotnetnuke website on the IIS 7 webserver on my laptop. The only way I have figured out to do it is to share the root directory of the site with IIS_Users and give IIS_Users read/write priveleges, however when I do that the whole application gets messed up and I have to reinstall it. Note that I cannot salvage the application at that point. I've tried preserving the web.config file and restoring it. I've tried restoring the entire directory. I've tried stopping the file sharing on the restored files. Nothing works but a complete reinstall of the entire application including the underlying database. It seems that Visual Web Studio 2008 Express is corrupting the entire application once it is able to make changes. There is no way I can figure out what it's doing to the application and why it is getting messed up because it is way too complex. I'm trying to use the free community edition to make some money, and then I might buy the professional tools, but the thing is if I can't even use free tools to work I'm sure as hell not paying money for tools that probably won't work with VWS either. The only thing I have figured out is how to make changes to existing modules with a text editor, which is a really sucky way to have to do things. I just want to be able to use the free Microsoft rapid application development tools right now to develop my modules for DNN. I'll learn the complexities of DNN as time allows. Why can't I find any good free tutorials on this forum? Surely somebody knows how to work with the free stuff.
By Dana Armstrong on
7/13/2010
|
|