Condivisioni di rete di Visual Studio 2012

Question

Emulo Windows 8 su una macchina virtuale utilizzando Parallels. Conservo tutti i miei progetti di sviluppo sulla partizione del mio Mac per semplicità e coerenza.

Quando si tenta di costruire un app (Visual Studio 2012) scappare questa condivisione di rete, ottengo il seguente errore di compilazione:

Error 1 Error : DEP0700 : Registration of the app failed. Rejecting a request to register from file:///Z:/Users/MY_USER_NAME/Sites/App1/App1/bin/Debug/AppX/AppxManifest.xml because the files are on a network share. Copy the files to the local computer before registering the package. (0x80073cf9) App1

Qualcuno sa come risolvere questo problema? Devo dire a Visual Studio 2012 che la mia condivisione di rete è un dispositivo fidato, o almeno l'ho ingannato pensando che il progetto si trovi in ​​un'unità locale. Esiste comunque la possibilità di creare collegamenti simbolici in Windows?

In Visual Studio 2010, ho risolto questo problema come descritto su questo sito: http://www.sehajpal.com/index.php/2010/10/how-to-solve-loadfromremotesources-error-in-vs-2010/

Grazie per l'aiuto!

Answer 1

This post by Gearard Boland risolve questo problema. Speriamo che questo è utile per chiunque altro lo sviluppo di più di una condivisione di rete:

Yes, it's by design that you cannot run a Metro app from a network drive and deployment from Visual Studio essentially registers the app with the system without actually packaging and installing it (so it doesn't get put into the normal install location, which is local).

You can still work with sources on a network drive, but you'll have to override the deployment location, which by default is under the project's root directory (e.g. bin\). You have several options:

1. You can switch from local debugging to remote debugging and set the machine name as 'localhost'. This will do a remote deployment on your local machine (thus not using the project's directory). You don't need to install the Remote Debugger tools, nor start msvsmon for this to work on localhost.
2. You can override the project's output directory. Right-click on the project and change the output directory to something like: $(Temp)\$(MSBuildProjectName)\bin\$(Configuration) , where Temp is an environment variable pointing to your Temp directory.

3. If you still want normal output to live next to the sources, e.g. when you build the appx package, etc., you can override only the layout directory instead of the entire output path. For this you'll need to modify your project file directly (e.g. *.jsproj, *.csproj, ...) to add the new value:

   <PropertyGroup> 
       <LayoutDir>C:\WorkingFolder\$(MSBuildProjectName)\$(Configuration)</LayoutDir> 
   </PropertyGroup> 
   

Hope that helps.