I have a project using the SpeechClient.dll from NuGet. The program runs fine on the development machine. So I have a Windows Setup Project that creates the installer. I run the installer and all the files show up including the SpeechClient.dll, but as soon as the program makes the first call to the Speechclient.dll, I get a
file not found
exception. This is the output from the event viewer.
Does anyone have any troubleshooting ideas? Thanks.
Seems now that I have installed visual studio on the machine that it is working. I wonder what visual studio installs? I was also trying to use Fusion Log Viewer to see what the problem was.
I had this problem as well. Installing the Visual Studio C++ Redistributable 2017 x64 cleared it up.
Related
The project I'm working on in Visual Studio Code builds fine when you use the Live Code from The Unreal Editor but if you try to build from Visual Studio you get this in the terminal...
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
I'm assuming it is choking on the space in C:\Program Files (however that is a standard space in that Windows created directory so I can't change it without breaking links for countless other files in that directory). As well when you build from Unreal it doesn't choke on that space - so I'm wondering if anyone knows how to "ignore" the spaces. And since Visual Studio 2019 has no issues building that project - it must have some setting that is also ignoring the spaces. Thanks in advance.
(it doesn't seem to fail - it just seems to soft lock? the "thinking spinner" just keeps spinning and it never seems to complete the build task).
I brought the same project into Visual Studio 2019 and it builds fine, however I can't get Unreal's Live Code to link with 2019 so I'm just trying to get this working in Visual Studio Code since Live Code works great with it.
Recently I upgraded a project to Visual Studio 2022. I am using command line to build the installer project (.vdproj) using the command something shown below
devenv.com <Solutionfile> /build <InstallerConfiguration>.
The command used to build file with VS 2019 but when trying to build the same with Visual Studio 2022 seems to be stuck. It seems that everything builds fine but the Visual Studio process does not exit after the project is built and causes the build pipeline to be stalled. I have disabled out of proc build to see if this was causing the issue but it does not help. Any one experience the same issue? I am using the most recent version of visual studio along with the Visual Studio installer project extension. Any other method of building the installer project? I have tried MSBuild command but it does not understand vdproj files.
This has been fixed with the latest release of VS 2022 17.3.6. Works fine for me now.
I am developing Unity game apps on a PC using C#, using Visual Studio Code as the editor. The apps are targeted at PC and Android. Multiplayer uses Photon Pun 2.
The Unity version is 2019.3.14F1 - I don't want to move forward just yet in case of 'unexpected problems'.
The VS Code version was 1.48.3 - and everything was fine, no compile errors, all code working OK etc.
Stupidly, I took Microsoft's advice to update VSC, and VS Code went to 1.50.1. Result of this is that there are all sorts of errors showing up in VS Code relating to the Photon code. All these errors stem back to the 'using Photon.Pun;' line. It says "the type or namespace name 'Pun' does not exist in the namespace 'Photon' (are you missing an assembly reference?)".
The code however does not come up with any compile errors in the Unity editor itself, and it all runs fine, including the Photon parts. The problem is in VS Code.
I realise this is almost certainly as VS Code problem, not Photon, but I am wondering if anyone has met this before and knows how to fix it?
(This is why I do not want to move from 2019.3.14F1 to 2020.whatever at the moment - you never know what might happen).
I had the same problem. Installing different versions of VS Code / VS Community Edition didn't fix anything for me, but this did:
With the project open in VS Code, find all occurrences of
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
in *.csproj files, and replace them with
<ReferenceOutputAssembly>true</ReferenceOutputAssembly>
Tried rebuilding project files, swapping to a different editor (VS Community Edition 2019 - that was fine), but no difference - VSC persisted with the errors. Rest of intellisense working OK.
In the end, totally uninstalled VSC and reinstalled, and that sorted it out. No idea what the actual fault was.
I was wrong.
To-day, the errors are back.
The reason appears to be that in the process of trying to sort this, I installed VS Community Edition 2019 to see if that worked OK (it did). Then went back to VSC, and - that was fine too. Later I uninstalled VS Community Edition 2019 (it is taking about 4GB). It was uninstalling that which brought the errors back into VSC. Reinstalled VS Community Edition 2019, and it is all fine again.
So, VS Community Edition 2019 installs something that VSC needs - but I haven't yet figured out what it is.
UPDATE:
Gave up. Never managed to find out what VSC wanted and wasn't getting. Instead, reinstalled old version of VSC (1.48.2 from code.visualstudio.com/updates) and it is all fine again.
If still having this problem, all you have to do to fix it is by going to Package manager and install "visual studio editor package"
windows>Package Manager> All Packages /or Unity Registry (depeding on your unity version) search of visual studio editor
if it's already installed delete it and reinstall.
Got it FIXED!
Solution (it was a Unity issue):
In Unity, goto Edit > Preferences > External Tools > External Script Editor, and point it to Visual Studio..
Why this was so hard to find, I have no idea. But now my Photon solutions and namespaces properly transfer from Unity to Visual Studio. Hooah!
Also moved the script to where the photon scripts are
Uninstall the Visual studio community and re-install with latest VSC 2022. It will fix the issue
As mentioned here I've tried to build the QGIS on Windows 7.
There are two methods one using Visual Studio Express Edition installer and the second one using MinGW.
I've found both of them broken and don't know what to do next
In building using Visual Studio
The link to visual studio actually installs the version 2010 but documentation assumes it version 2009. So "set VS90COMNTOOLS=%PROGRAMFILES%\Microsoft Visual Studio 9.0\Common7\Tools\" path is not found.
Also I'm confused about the context of this line:
If the path to bison and flex contains blanks, you need to use the
short name for the directory (i.e. C:\Program Files should be
rewritten to C:\Progra~n, where n is the number as shown in `dir /x
C:``).
In Building using MinGW 4.2.1. MSYS link is not found(404) but when I try to build step by step I find XDR 4.0 not found(404) in this page
So what's the way to build it?
All I want is to change the title and startup photo of QGIS Desktop software.
Using another application I'm now able to change the title of running QGIS but don't know where to change the photo which shows "Loading plugins...".
The build instructions for Windows 7 are a tad long in the tooth, but they work for the most part. I did not try MinGW.
I immediately changed the VS90COMNTOOLS path to point to the Visual Studio 2010 directory and it seemed to work for me:
set VS90COMNTOOLS=%PROGRAMFILES%\Microsoft Visual Studio 10.0\Common7\Tools\
Regarding bison and flex configuration, I used the latest version of CMake (3.3.1 as of now) and didn't encounter any warnings/errors pertaining to bison or flex. Are you encountering any right now? If not, you should be able to proceed.
I was tring to deploy an ASP.NET Web Application to a Windows Azure Web Site by following the tutorial through this link: https://www.windowsazure.com/en-us/develop/net/tutorials/get-started/
After download the public profile, which is a ".PublishSettings" file, I go back to Visual Studio and right-click the project in Solution Explorer and select Publish from the context menu as the tutorial said. However, a warning box jumped up and it showed me that "The Web Publishing extension is not installed which is required to publish. You can install it from http://go.microsoft.com/fwlink/?LinkID=208120."
I already installed "Windows Azure SDK for .NET (VS 2012)" and I also tried to uninstall this and install again, but the same problem is still there.
Anyone knows how to solve this? I am really appreciated.
I ran into 2 issues, which were related. One was the web publishing extension is not installed which is required to publish, and the other was the web extension package did not load.
I'm upvoting and reposting user3918092's solution for others who run into this issue and do everything including:
Deleting the ComponentModelCache out of
C:\Users\...\AppData\Local\Microsoft\VisualStudio\12.0 and
C:\Users\...\AppData\Roaming\Microsoft\VisualStudio\12.0
Repairing Azure SDK 2.4 and VS2013U3 Uninstalling and reinstalling
both Azure SDK 2.4 and VS2013U3
Removing extensions from the solution
Ignoring the extensions on VS startup
Using devenv /setup and devenv /updateconfiguration to try to reset the configuration
The solution is:
Reinstall the following items to your GAC using the following commands from the vs command line run as an administrator:
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Internal.Contracts.dll"
Thanks to user3918092!
I had the same problem on Visual Studio 2013 (Asp.net and web tools 2013 extensions have not been installed)
Solve it by re-install Visual Studio 2013 update 3.
http://www.microsoft.com/en-us/download/details.aspx?id=43721
This has worked for me.
I had Visual Studio express 2012 then installed Visual Studio 2013 needed the azure tools so I installed 2.4. I lost publishing at this stage and
unistalled Visual Studio express 2012.
So that is how I think it got out of kilter.
The solution was to reset the assemblies for Contract and Publishing using the Developer command prompt as Administrator.
If you have used the default installation setting then this is probably the path
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Internal.Contracts.dll"
Same issue with Visual Studio 2015.1 after installing a Web Tools update.
The assmeblies that have to be installed into gac are now:
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.Core.Contracts.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.Contracts.dll"
I have the same problem. After reinstalling VS 2013 update 4 and Azure SDK 2.6 problem still persists.
But then I tried the next thing:
In section Control Panel > Programs > Programs and Features select and repair Microsoft ASP.NET and Web Tools 2013.4.
And publish option started to work again.
I had this issue upgrading VS 2013 Ultimate from update 3 to 4. I had also a message about Microsoft.VisualStudio.Web.PasteJson.JsonPackage did not load properly when loading a Solution.
Repairing VS was enough for me to work again the publishing option.
http://connect.microsoft.com/VisualStudio/feedback/details/758298/not-able-to-publish-web-application-after-installing-visual-studio-2012-rtw has a work-around but it's a painful reinstall with additional folder deletion.
register GAC also work when have this problem after update VS 2013.2 to VS 2013.3
I had similar problem, but my error is related to scaffolding item.
I need to uninstall visual studio and went through all the related folders, registry and re-install visual studio in order to make it work!
Folders that I checked:
%App Data%
%Program Data%
%Program Files%
Windows
Hope that help :)
I uninstalled VS2012 again. Before I re-installed (a 3rd time), I went to my user's AppData and Documents folders and found all instances of Visual Studio 2012 and deleted them. Then I re-installed VS2012 and now Web Publishing is working.
Folders I deleted after uninstall:
C:\Users\USERNAME\Documents\Visual Studio 2012
C:\Users\USERNAME\AppData\Local\Microsoft\VisualStudio\11.0
C:\Users\USERNAME\AppData\Roaming\Microsoft\Microsoft Visual Studio\11.0
C:\Program Files\Microsoft Visual Studio 11.0
C:\Program Files (x86)\Microsoft Visual Studio 11.0
I had this happen today out of the blue for a vs2013 project that was publishing fine previously.
I solved it by downloading a 'Visual Studio Web Publish Update' package from here.