I have a Windows Forms application that I am using ClickOnce deployment for and everything publishes fine when I am attempting to publish in Windows XP. When I try the same publish feature in Windows 7, it hangs on the publish step.
I am using a UNC path (file share) to the server (Windows Server 2008 R2 with IIS 7). Why might this happen?
I never receive an error message and the process cannot be cancelled. I have to force-close Visual Studio and restart my Windows 7 PC because Visual Studio has some of the files locked.
UPDATE:
I was able to set full-control permission on the folder on the destination server for my domain PC, and I was then able to publish once. Then, every subsequent deploy hanged. I did notice however that it always hangs when it's trying to copy the Office Interop files. Why would this be?
UPDATE (2):
This is definitely related to the Office 2010 PIA files. Why would it not publish them? Again, this works flawlessly on Windows XP, but when I perform the deployment on Windows 7, the PIAs are not published.
It could be a UAC issue. Try running Visual Studio as an administrator when you do a publish.
Related
When I try to deploy from a developer machine that is on another domain the deployment fails.
Visual Studio gives me this Message:
The Visual Studio 2015 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
Works fine when I deploy from a machine that is not in a domain.
I've been searching the web for days now but I'm not able to find any solution yet.
I'm guessing you have Windows 10 IoT-Core Build 10586 on your Pi, but you don't have Visual Studio 2015 Update 1 installed. You need to use the new Universal (Unencrypted Mode) authentication method with build 10586. You can read more about this issue here: http://embedded101.com/Blogs/David-Jones/entryid/721/Win-10-IoT-Core-Visual-Studio-2015-Update-1-App-Deployment-and-Debug-Requirements
I recently developed an WinForm application that I wanted to run on my local SQL server using SQL Agent. I published the WinForm app via Visual Studio and copied the files (three listed below) over to my SQL Server where I ran the setup.exe program.
Application Files (directory)
MyApplicationName.application
setup.exe
My application installed and started up automatically.
Now that I have to schedule the job with SQL Server Agent I cannot find where the application was installed to on the filesystem. I can see the shortcut on the Start menu but it just points to a shortcut. The shortcut does not seem to have any indication as to where the actual application file exists.
I tried to point to the shortcut as the application SQL Agent should start but all I get is "junk text" in the path.
Visual Studio uses ClickOnce deployment to publish WinForms applications. The installation folder varies by Windows version. For example on Windows XP it is
C:\Documents and Settings\USERNAME\LocalSettings\Apps\2.0\
and on Vista and above it is
C:\users\USERNAME\AppData\Local\Apps\2.0\
I have this bizarre scenario happened to me today morning. I was scheduled to publish a new version of my application and I did it successfully (as Visual Studio 2012 output said!). The Publish HTML also had the correct version in it.
Note
- Development Terminal runs on Windows 7 SP1 with Visual Studio 2012 Update 4,
Crystal Reports 13 for Visual Studio and Kaspersky EndPoint Security 10 for Windows;
- Files are copied over a FTP to a Windows Server 2003 server within the LAN;
- User Terminals are loaded with Windows 7 SP1 and Windows XP SP3 with Kaspersky EndPoint Security 10 for Windows;
When I checked with Users, some said new release weren't applied in their terminals. Further investigation revealed that those whom had Windows XP, had itself updated with the latest release, where as those whom had Windows 7 did not detect any updates available and runs the previous released version when ran without any errors.
Further, I noted that in Users who were having Windows 7, if the Application is Run from Start-up menu it loads the previous release which had been there earlier. I tried uninstalling and deleted all contents in
C:\Users\\AppData\Local\Apps\2.0*
and launched the application from Publish.html web page again. Then I noticed that it prompts for installation and when I clicked "OK" it only installs an application with 6.95MB where as the new application is 7MB+. This proves that ClickOnce picks the previous release from some where, which I cant figure the location. I even tried up increasing the Publish Version thinking it will detect a signature change but did not. :(
I have checked the Manifest file in the server, it had the latest version specifying in it.
Let me know of any location where I could further investigate; I mean where does ClickOnce stores all files other than C:\Users\\AppData\Local\Apps\2.0* and where I could find the Log file which ClickOnce creates which I'm struggling to find
I have published releases earlier, but this is the first time I'm getting such problems. Since my last release which I publish, I had only installed Update 4 for Visual Studio.
Did anyone come across it?
These were my Settings:
Everything worked today morning. It seems, some client level cache was a reason to this problem in Windows 7 users.
Should I have urged the users to re-start their machine, this would have not caused; I presume. But nevertheless happy that everything went on board with the new update.
I've Visual Studio 2012 Ultimate on Windows 7 x64 machine.
Today when I tried to run my WPF application I got this error :
What's wrong ? What is remote debugging ? I just want to run my application.
I've also lunched "msvsmon.exe" but it didn't fix my problem.
Restarting my machine was another way to get rid of this problem that I tried.
How do I fix it?
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
I you are running Proxifier add a rule to route ::1 (IPV6 Loop-back) Direct and not via the proxy.
I had the same problem. It was because of some tunneling software on my computer: Proxifier.
If you run it, after then this error will appear when you hit F5. However, closing the Proxifier would not be enough! You should close it, then close the VS, after then, reopen the VS.
Select 'Local Machine', when you run the application. It seems like Remote Machine is selected for debugging.
I was developing an Application that requires a database to store and retrieve data. I am developing the applcation on Visual Basic 2010 Express Edition and using SQL Server Compact Edition for database, on a Windows 7 PC. The Application works perfectly on Windows 7 on my PC. The problem arises on the system of my client who is using Windows XP.
I asked him to install .NET Framework 4.0 and SQL Server CE and send him a copy of the build Application. But when he executed the application and reached a form where database was being used, he encountered and error saying "Access to the database file is not allowed. [ File name = D:\prototype\app\master.sdf ]" and on clicking on continue the form loads but data from the database is not loaded, since it's not connected.
The same problem occurs on windows 7 if i copy the app folder to Program Files directory on Windows 7. But It doesnt occur if i execute the application as "Run as Administrator"
So I require your help to figure out what might be going on and why can't the application access the database simply as it is working on windows 7 (except in the program files directory).
Thanks in advance,
Best Regards
"The user need read-write access to the database file, so you must put it in an suitable location, and change your connection string accordingly."
http://erikej.blogspot.dk/2011/02/using-sql-server-compact-40-with.html
By EricEJ