I emulate Windows 8 on a VM using Parallels. I store all of my developer projects on my Mac's partition for simplicity and coherence.
When I try to build an app (Visual Studio 2012) running off this network share, I get the following compile-time error:
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
Does anyone know how to solve this issue? I need to tell Visual Studio 2012 that my network share is a trusted device, or at least dupe it into thinking the project is in a local drive. Is there anyway to create symbolic links in Windows?
In Visual Studio 2010, I solved this issue as outlined on this website: http://www.sehajpal.com/index.php/2010/10/how-to-solve-loadfromremotesources-error-in-vs-2010/
Thanks for the help!
This post by Gearard Boland solves this issue. Hopefully this comes in handy for anyone else developing over a network share:
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:
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.
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.
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.
Related
Firstly the solutions I have found yet in various websites, are for older Visual Studio versions.
My configuration is:
Visual Studio 2015 installed in Windows 10 virtual machine
(VMware)
A shared folder which is treated as a network drive and mapped as Z:\ in the VM
What I can do successfully:
Creation, loading and debugging Visual C# Windows Forms Application in the network drive in the VM
The same above for Visual C# ASP.NET Web Application but only in a local drive
What I cannot do successfully:
Creation, loading and debugging Visual C# ASP.NET Web Application in the network drive in the VM
Error messages I get:
During creation: Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL)) error message
During loading: If a Visual C# ASP.NET Web Application project is successfully created in a local drive, moved to the network drive and then opened from the network drive in the VM, I get the error message:
Creation of the virtual directory http://localhost:2648/ failed with the error:
Filename: \\?\Z:\Test Projects\WebApplication1\.vs\config\applicationhost.config
Error: Cannot read configuration file
But the configuration file applicationhost.config is still there.
How to solve the issue for the above given configuration?
It looks like a permission issue to the file.
Double check the identity you are using for your site (in IIS) Network Services, Local System or whatever
In IIS under Application Pools under 'Advanced settings' get
the pool identity name.
Give full access to that identity for your web.config file
(even better for the whole folder application)
Do the same for IIS_IUSRS group
I have made a workaround for the issue. I have both a local folder and a shared folder for the same ASP.NET project. I always open the SLN file (project solution file for Visual Studio) from the local folder in the VM. I periodically run a process in the VM to synchronize the changes in the both folders (local and shared) so that both folders can contain exactly same files. I actually use FreeFileSync app for it. In this workaround, file merge conflict may occur if same files are edited both in the VM and the host before last synchronization. In this case I can review the changes in the conflicted files to resolve conflict. My answer is really a workaround but it works.
I have an application that works fine in my computer locally. What I need is to run this application in another computer but it doesnt have Visual Studio.
I installed IIS 7.0 and tried to create a virtual directory but no luck. Am using the right port? Used port 80 and tried port 4444 and no luck. Any ideas?
What files do I have to drag into the inetpub/wwwroot? All my project files?
You don't need Visual Studio for a web application (aspx). You need to copy the files from the Bin folder and setup a Virtual directory (you do need IIS and might need to enable some features in IIS to support ASPX) .
The easiest way to do this is from Visual Studio right click your project and click Publish. This will let you select what kind of publish option you want (File System will publish to a local dir and you can just copy to the new computer and hook to the virtual directory you created, Web Deploy let's you remotely publish from your local dev box, etc.)
Here is a walkthrough
As long as you're accessing the ASPX files through an IIS web server with the correct target framework you used then it can easily work without Visual Studio.
For instance, my production servers don't have Visual Studio on them. They just need IIS and the proper .NET framework installed.
As a commenter mentioned above, if you right click on your project and select PUBLISH you'll be in good hands.
Go to IIS Manager
Open sites
Right click on default website and choose "Add Application"
Alias "Application Name 'can be any' " and Physical Path is the application path
My setup is:
Debugging computer:
Visual Studio 2008 Professional
Domain access
Application-running computer:
MSVSMon.exe
Workgroup only
Both computers:
Windows XP pro
Same local username and password
Access to same workgroup
I log into the same local username and password on both computers (username == "debugger"), and point VS 2008 to the remote computer, "Robot," under Project Properties > Use Remote Machine, and instruct VS to debug. In short, I followed the directions here and here. A ten second hang ensues then an error:
Error while trying to run project: Unable to start program '......\prog.exe'.
The system cannot find the path specified.
A few extra notes:
I tried "run an external program" pointing to the output of the project to no avail.
I'm not trying to debug an ASP.Net application.
The project source is on the local computer.
Please let me know if you have any solutions or leads. Thanks.
Make the executable and debug symbols accessible to both computers: in a shared or shareable directory. Make the debugging computer's project "start an external program" being the shared directory from the point of view of the application-running computer.
EDIT
Also, be sure that you are careful that you run the correct build. Don't run the Debug build remotely if the debug framework isn't installed on the remote machine!
I'm trying to deploy a WinForm app through clickonce using a ftp site on my dreamhost account. However, when I try to publish, I get the following error:
Failed to connect to 'ftp://ftp.mydomain.com/client' with the following error: Unable to create the Web site 'ftp://ftp.mydomain.com/client'. The components for communicating with FrontPage Server Extensions are not installed.
Here is my settings on the publish tab
Publishing Folder Location: ftp://ftp.mydomain.com/client
Installation Folder URL: http://ftp.mydomain.com/client
It seems that Visual Studio is not realizing I am publishing to a ftp site and not a site with FrontPage.
Does anyone know how to fix this problem?
Visual Studio only supports publishing to web servers that have Frontpage Extensions installed, regardless of whether connecting via FTP or HTTP. If your host doesn't support them, you will have to publish to a local folder and then upload its contents using an FTP client.
UPDATE: The FrontPage extension components need to be installed on the machine you are DEVELOPING on (Used to publish). The server shouldn't matter--it's simply FTP. On your development system, go to control panel > add/remove programs > and repair "Microsoft Visual Studio Web Authoring Component". Depending on the version you have, you may need to repair VS2010, etc. This will reinstall the FP components on YOUR machine, allowing you to publish via FTP.
Do you recently installed Xamarin extensions xamarin.visualstudioInstall.msi ?
This is cause of stopped deployment component.
Check this discusion:
http://forums.xamarin.com/discussion/30406/bug-after-installing-xamarin
Removing 'Xamarin' from the uninstall/change a program fixed the issue for me.
After that VS 2013 and VS 2015 RC1 deployments started to work again.
what is worth of acknowledgment is the fact that Visual Studio 2010 may report such error due to problems with lacking RAM or after several sleep or hibernation phases with VS turned on. I experienced this with a perfectly well configured server which I have used for ages and done hundreds of publishes, the error came all of a sudden and the only medicine was a VS restart (or sometimes the whole machine's restart). Best regards.
According to MSDN specs, you'll have to add some custom content/mime types to your server for ClickOnce:
If you are deploying a ClickOnce application from a Web server
other than IIS, you may experience a problem if the server is
returning the incorrect content type for key ClickOnce files, such as
the deployment manifest and application manifest. To resolve this
problem, see your Web server's Help documentation about how to add new
content types to the server, and make sure that all the file name
extension mappings listed in the following table are in place.
File name extension Content type
=================== ===========================
.application application/x-ms-application
.manifest application/x-ms-manifest
.deploy application/octet-stream
.msu application/octet-stream
.msp application/octet-stream
DreamHost allows you to add custom mime types in a .htaccess file.
I have created a setup for my windows application in .NET 2008
After building the same i have the .msi and setup.exe files in my release folder.
The problem i am facing is :
I can install the application using the msi installer files from the shared network folder. But when i copy the installer locally and tried to install it,
i get the following error: Error reading file.Please Try again.
Anybody having any ideas if there are any properties to set in the installer project.
Regards
Constant Learner
Just a thought, you can use Orca to go through the .msi and see if you're having any static references to your development machine within your msi.
The application is a simple windows application without any database associated with it.
Its just a hello world windows application. So i presume its something related to the configuration part of the installation...
Constant Learner