All,
I am using the VS2010 database connection dialog that Microsoft have released (download from here). I am using this without any problems on Windows 7. However, when I install the application on Windows XP (using the 'Publish' option in VS2010) I get the following error
Using NSIS, the application installs but upon trying to launch the VS2010 dialog I get the following error
Clearly the first error is telling me what the problem is, but as I have never come across this before I am not sure what I can do to address/fix it. Could this be associated with not using the manifest correctly?
As always any help is most appreciated.
Seems that in your Windows XP is missing the library for Microsoft SQL Server Compact 3.5
You could download the bits from here
Related
I just unpacked my new laptop on Windows 8, and installed the latest version of Visual Studio Ultimate 2013.
Through the server explorer view I tried to add a new connexion to a sql-server database. (Connect to database button)
Each attempts to log-in finished by a crash of visual studio.
Then I tried to get more information about the issue using VS as a debugger for itself.
It seems that msvcr110_clr0400.dll thrown an exception.
Just in case here is the disassembly :
I tried and re-tried several times, checked for updates, installed an other version of vs (Ultimate2012).Any clue how to fix this ?
Require repair installation of .net 4.0 (or 4.5/4.5.1).
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 am facing VSTO error when I am trying to install the application using click once installer. I have tried on Windows XP machine and also on Windows 7 machine.
Exact error when opening the application on client machine is
“The following Microsoft solution cannot be loaded because a compatible version of the .NET Framework is not Installed: myApplicationName.vsto”
The application is VSTO app in C# with WPF tab embedded in Excel application (Framework 4).
The framework the application is developed on is already installed on the client machine.
I did not find any solution in this thread; any help would be highly appreciated.
I had the same issue today. I believe this is a problem with the VSTO 2010 installer included with your application.
I went and downloaded the latest version from Microsoft, installed it, retried my installer and then everything worked.
I have a Windows Forms (C#, SQL Server) application that I developed up and running and all is well, except for when I try to run its Release .exe on my own development workstation, it issues the "The publisher could not be verified" warning.
(When I run this application from Visual Studio in Debug mode, I don't get this warning)
I know about code signing but this application is going to be installed on a single machine only (directly by me, on the client's machine), so I am thinking perhaps there is a way to get rid of this warning without having to sign the EXE, similar to the exception Microsoft does when running from Visual Studio?
Note: on a single install single machine only.
Is this possible?
Are your running it from a network share by any chance?
If so, try copying it to a C:\ folder and see if that solves the problem.
When I run my application (WPF,VB.net 2008) on Windows XP, I get weird Windows Errors. When I installed VS2008 on the machines that got the error and debug. I got a loader lock exception, so I went into Debug and removed it. However, I still get the error when it is installed on the machine.
Is there a way to remove the Loader Lock Exception when the application is install. I do understands that it might not be the best solution, but it seems this happen only when I start an WindowsElementHost with a ReportViewer and this is causing the problem, so I don't really know what else to do with it.
All version of XP have that problem, as with 2003.
In Windows 7 and Vista I never run into that error while debugging and the installed product. The same thing applies with 2008 and 2008R2.
I've done a little bit of research and below you can find my guesses:
maybe it's a bug in the Report Viewer control itself and you should update to a later version. I've noticed that on December 2012 a new version was released (see this post), supposedly running on both .NET 3.5 and 4.0 (so it should work with VB 2008, see download page);
I've noticed that Report Viewer 2008 SP1 requires .NET 3.5 SP1 (see the download page) -- maybe an outdated version can trigger the exception you are seeing;
maybe Windows XP is not updated to the latest Service Pack or is the wrong edition -- again Report Viewer 2010 SP1 requires Windows XP SP3 (see download page) and Report Viewer 2012 does not run on Windows XP Starter Edition;
maybe it's a library used by Report Viewer that causes this exception (especially a mixed mode assembly) -- a dump or a stack trace would be helpful in this sense;
there is a comprehensive answer in this thread in the Visual Studio Tools for Office forum that lists several resources to understand this problem;
the previous link suggests that in some conditions it's safe to ignore this lock. If from your testing under Visual Studio with Loader Lock MDA disabled you see that there is no problem, you can disable the MDA in production machines using the instructions in this blog post -- basically it involves setting an environment variable and adding some lines to the app.config file (see also the documentation for Loader Lock MDA to see what the new lines should look like). I haven't tried it but I thought it may be useful for you as a last resort solution -- just be sure to test thoroughly your application to avoid undesired side effects.
To get more help, I suggest you so specify:
the version of Report Viewer you are using;
the version of .NET Framework you are targeting (in particular including Service Pack);
what Service Pack is installed for Windows XP;
any stack trace or debugging information you can gather.