Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Connect VS to a virtual machine?Connect VS to a virtual machine?
Previous
 
Next
New Post
2/24/2009 2:29 AM
 

While the first days I was developing DNN on my local machine, since a couple of days we moved to a development server. Our IT admin made me a virtual machine, so I connect from my desktop with a Remote Desktop Connection (have an IP, username and passwort, administrative rights).

Is it possible to still use my local machine and local VS (Visual Web Developer 2008 Express) with that? In particular:

  • Use my local browser (on the virtual machine I can open DNN by http://localhost/DotNetNuke but when I try to connect on my local machine with http://IP-from-virtual-machine/DotNetNuke it simply says the site is under construction)
  • Use my local VS IDE so that file changes are made directly on the server/virtual machine?
 
New Post
2/24/2009 3:20 AM
 

 it depends, if you have file access from your local machine to the central code base, but IMHO either develop locally or use the dev server - I assume any combination will only increase issues.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/24/2009 4:23 AM
 

I just want to save the time I have to spend transferring files from my local machine to the virtual directory. Furthermore I am worried that some things might work on my local machine but then cause errors on the server.

I found that VS can connect to so called remote sites. Therefore they have to support Frontpage Server Extensions. But although I get to this site: http://www.visualwin.com/FPSE/extend-site-main.png it then hangs on the following loading-screen: http://www.visualwin.com/FPSE/extend-progress.png

 
New Post
2/24/2009 4:46 AM
 

Hi Jens,

Can you create a share on your local machine that points at your codebase ?  Then go to IIS on your virtual machine and set the source directory for the site to be this new share?  That way you can continue to develop as you do now and have your virtual machine updated immediately, without requiring file transfer.

Barry

 
New Post
4/1/2009 1:42 AM
 

BarryS wrote

Hi Jens,

Can you create a share on your local machine that points at your codebase ?  Then go to IIS on your virtual machine and set the source directory for the site to be this new share?  That way you can continue to develop as you do now and have your virtual machine updated immediately, without requiring file transfer.

Barry

I have done exactly this, but I get problems when trying to configure Frontpage Server Extensions in the vitrual over a UNC share.  Has anyone solved this issue?  I'm running Server 2003 in the VM and XP64 locally.    I have seen other forum posts mentioning creating 2 registry keys:  AllowUNC and NoMachineGroups... but this hasn't solved the problem.

Opening the DNN VS2008 solution fails on the DotNetNuke_Cambrian project.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Connect VS to a virtual machine?Connect VS to a virtual machine?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out