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.
Related
I have a problem which I struggle for 3 days. It seems that my Visual Studio Community 2019 doesn't want to recognise the ".Net core" for Windows Forms. I even install it manually (downloaded from Microsoft - .NET Core 3.1 SDK) but doesn't help. I used this blog Microsoft blog. They said that I have to install " Windows Forms .NET Core Designer VSIX package" because "it isn’t yet bundled with Visual Studio", but there is no link to download. I don't have ".NET Core" in "Project solutions" and "Visual Studio Installer" (I cannot download it from the installer). The version of VSC 2019 - 16.8.2
SS:
Installer
Project Picker
Installer2
Settings
So I had the same problem and yes you can't find .NET core windows form directly to open windows form that support windows form you will need to first open non .NET framework windows from app there you can select if you want core which version.
Windows Form Application
Selecting Desired Framework
You'd have to select Windows Forms App (.Net) from the available project types and that will open up as the latest .NET core Windows Froms.
Visual Studio (VS 2017) has started failing to deploy to my IoT device ... I recently started using a more recent version of Windows 10 IoT Core (upgraded from build 17134 to insider build 17692) and Visual Studio can no longer deploy UWP apps.
The reported error is:
DEP6957: Failed to connect to device [IP Address] using Universal
Authentication. Please verify the correct remote authentication mode
is specified in the project debug settings. COMException - Exception
from HRESULT: 0x801C0003
The IP address is valid and VS can see the device.
This seems to be an error reflecting a mismatch between the Windows SDK installed on the Visual Studio machine and the OS version on the IoT device.
For recent versions of Windows 10 IoT Core (I'm using the insider images that you can install through the Windows IoT Dashboard), a recent version of the Windows SDK (I used Windows 10 SDK 1803) must be installed on your deployment machine.
Also uninstalled and reinstalled UWP parts of VS as described above.
Finally, I clicked on "update" for the whole VS installation (Visual Studio Installation program). Drew 4GB out of the net over night and in the morning everything was working as it should...
I've developed a Lync Silverlight application and it is working on my local machine. Then I needed to add this Silverlight to a Sharepoint site, thus i used Silverlight web part. It is OK on my local Sharepoint site but when i install it to server i could not see the Silverlight and not getting error.
I am using web service on my Silverlight application. I check that server can access to web services. My development environment is Visual Studio 2010 and Lync Server 2010. Also I am using Sharepoint 2010.
Here is what i tried for the solution:
Check the whether IIS is configured for xap - OK
I tried to install xap file through Sharepoint module, it did not work.
I tried to use a visual web part, it did not work.
I tried to embed xap file to an HTML page for debugging, there was no error.
Now i am stuck. Any suggestion will be appreciated.
Have you cross-verify with which Silverlight sdk version you have developed your silverlight application.
And server is having that version installed?
if it's working fine with your local server then it also works fine with another server.
regards.
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
I have a .NET WinForms application that I've converted into a COM dll using the Interop Forms Toolkit 2.1. Thet setup project for the application has both my tlb as well as the Microsoft.InteropFormTools.tlb file set to Register as vsdrpCOM. The prerequisites for the project are to ensure that Windows Installer 3.1, .NET Framework 3.5 SP1, and the Microsoft Interop Forms Redistributable Package 2.0a is installed.
When I run this locally on a Windows XP box with both Visual Studio 2010 and Visual Studio 6 installed, it works fine. However, on this Windows XP machine, I receive an error stating: "Class does not support Automation or does not support expected interface."
Any ideas?
I got it. For those of you that are running into the same, do the following:
Go into Visual Studio 2005, 2008, or 2010 (I used 2010) and build your Interop Form.
Then, go into Visual Basic 6. If your library is not already referrenced, reference the
library.
Build your VB6 executable.
Go back into Visual Studio (.NET version) and build only your installer. This way the installer and VB6 both have the same .tlb file
You're good to go. Thanks for the suggestion Kris!
You have RegAsm the assembly (see stackoverflow for more) on the machine you want to install the application on. The assembly should also be in the directory where the VB6 application runs, or installed in the GAC.