Could not load file or assembly Microsoft.ServiceHosting.Tools - c#

I just got a new workstation set up and I installed VS 2013 with Windows Azure SDK 2.3 first. But then I realized that our project was built upon Windows Azure SDK 2.2. So I uninstalled the SDK 2.3 and then installed 2.2. After that, I got the project from TFS and tried to run it and there was a problem:
Cannot debug the project because some run time file was missing.
So I tried to repair it by uninstalling Windows Azure SDK 2.2 completely and repair my VisualStudio.
But now I get this error message:
Could not load file or assembly 'Microsoft.ServiceHosting.Tools, Version=1.0.0.0, Culture =neutral, PublicKeyToken=232wedsfd3f4' or one of its dependencies. The system cannot find the file specified.
I looked through the project and there wasn't any reference of Miscrosoft.ServiceHosting. And the database and cloud are working. No idea what happened in the machine since Azure is a new field for me. Does anybody ever meet the same problem?

In my case, I have VS 2012. I was trying to develop an Azure web service. The error I'm encountering was
'Could not load file or assembly ***'Microsoft.ServiceHosting.Tools'***'
The issue was resolved after installing Microsoft Azure Emulator and
Microsoft Azure Storage Emulator.

I found the cause to be a corrupt Azure SDK installation on my machine with VS.NET 2013.
Reinstalling the Azure SDK from here (http://azure.microsoft.com/en-us/downloads/) and restarting VS.NET to clean and build the solution worked for me and got rid of the build error from the OP.

I finally solve the problem! But I won't delete the post because I think some other people might meet the same problem.
My problem was caused by OS (Win8.1 Ultimate) which doesn't support Hyper-V so that Azure Emulator couldn't be installed. After installing Windows Pro or Enterprise the problem will be solved!
Hopefully can help somebody who run into the same problem as me.

Reinstalling MicrosoftAzureComputeEmulator-x64 and MicrosoftAzureStorageEmulator solved the issue. No need to install the full Azure SDK again.
I faced same issue and reinstallation of above 2 softwares and restart of visual studio fixed the issue.

Related

Could not load file or assembly 'Microsoft.Azure.Storage.Emulator.Controller'

I hate to turn to StackOverflow for troubleshooting these types of things, because I feel that most issues should be able to be resolved through spending time Googling around for similar issues, but I've had so many issues with Azure that it's driving me insane.
I have just opened a brand new project, Cloud > MCV4 > ASP.Net Web Role. Rather than make any changes, I've just went to run it straight away to see if it works - it should. However I get this error message:
Could not load file or assembly
'Microsoft.Azure.Storage.Emulator.Controller, Version=4.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.
The system cannot find the file specified.
Now, I've had a look online and saw another Stack Q about this, here:
Azure Connection Error with Emulator
I did have Microsoft Azure Tools for Microsoft Visual Studio 2015 v2.8 and
Microsoft Compute Emulator v2.8 - but I have since downgraded them to match the versions in the link provided, however, I'm still having no success.
Anyone have a similar issue or can give me a couple of other things to try.
I've tried this both on VS2013 and VS2015 same error message
I have same problem with expanding Azure / Storage / (Development) branch in Server Explorer window in VS2015.
Solved by uninstalling (via Add-remove programs) Azure Storage Emulator (v4.6 currently) and installing older one - v4.5 from older SDK. I used August 2016 (version 2.9.5) version of Azure SDK for .NET (file AzureStorageEmulator.msi from there).
Now my VS2015 and 2017 works OK.

UWP (Windows 10 APP) - appcert.exe crashes before my app get tested

I've developed an simple and small Universal Windows App that uses EF7 and SQLite. The app builds normally and it runs perfectly from Visual Studio. I also can run it directly from Windows 10 in the start menu after the I side loaded it (once the app package is generated).
My problem is that I can't test the app after it's package is generated because of an error on appcert.exe.
If I generate app package to x86 when launching windows app certification from visual studio right after the package is generated I get the error "the appxbundle could not be implanted" even before the test starts.
If I generate app package to x64 when launching windows app certification from visual studio right after the package is generated the test starts normally but before it's done I get the following error: "an unhandled microsoft .netframework exception occurred in appcertui.exe".
The appcert.exe crashes and does not tell me why.
I've searched in google and I've looked at windows log event but found nothing helpful.
I just don't know what to do. My app is finished, I can generate it´s package but I can´t generate the ".appxupload" because of this error I mentioned.
Can someone help me?
The file C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll is CLSID {3866CD68-0FC3-4563-8888-E107295BC485} on my machine.
I was able to reproduce your crash by unregistering binaryinfo.dll on my machine and clicking "Validate Store App".
Maybe a fix for your issue to do register this dll (maybe all of them?).
From an administrator/elevated command prompt
regsvr32 "C:\Program Files (x86)\Windows Kits\10\App Certification Kit\binaryinfo.dll"
How your machine got into this state...unknown.
I've made a fresh install of Windows 10 and its SDK in a virtual machine on Virtual Box. The appcertui.exe is running fine and my app was tested successfully.
It might be a problem in the installation of the .NET Framework since I updated from Windows 7 to Windows 10.
I will try to completely reinstall both .NET Framework and the SDK to solve this issue. If none of this works I will reinstall Windows 10 from scratch on my computer.

LibSass.x64 not found on Azure VM (virtocommerce)

I new to ASP.NET development and I have managed to deploy VirtoCommerce to my local machine IIS (windows 8.1) following the documentation on http://docs.virtocommerce.com/display/vc2devguide/Deploy+web+applications+to+dedicated+server .
When I tried to deploy it in Azure VM running Windows server 2012, I got the following error when I tried to run the frontend page. The dll mentioned below is definitely in the /bin folder of the store.
Server Error in '/' Application.
Could not load file or assembly 'LibSass.x64' or one of its dependencies. An attempt was made to load a program with an incorrect format.**
I followed the link
Could not load file or assembly 'LibSass.x64' or one of its dependencies in VirtoCommerce but found no luck. What did I miss on this deployment ? Any help is much appreciated, thank you.
Are you running 64 but machine and IIS Application Pool as 64 bit? If not, make sure to go to IIS and configure pool settings to run as 64 bit process. The easier approach will be to follow the guide here: http://docs.virtocommerce.com/display/vc2devguide/Deploy+from+GitHub+to+Microsoft+Cloud+Azure which will setup Virto Commerce as a website in IIS with all correct configuration for IIS. You can then update it manyally by simply uploading site through FTP if you want. You can also clone the repository on GitHub and that way your azure site will auto update on every checkin.
I was able to reproduce this error on a clean Windows Server 2012 Standard. It turned out that Libsass.Net requires Visual C++ Redistributable Packages for Visual Studio 2013. After installing the vcredist_x64.exe the error has gone.

How to build Windows Store 8.1 app without Visual Studio?

I need this for the build server - I'd like to avoid installing full Visual Studio there.
I use the newest v12 MSBuild to build the solution with the app. Installing .NET Framework 4.5.1 and Windows 8.1 SDK got me through several compilation errors. With all that installed, right now, I get this:
error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\WindowsXaml\v12.0\Microsoft.Windows.UI.Xaml.CSharp.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
The targets file is present on my development machine with Visual Studio 2013 installed, so I guess it got there with VS 2013. When I tried to paste the whole folder to the build machine (I know, a stupid thing to do), I got the following compilation warnings and errors:
warning MSB3644: The reference assemblies for framework
".NETCore,Version=v4.5.1" were not found. To resolve this, install the
SDK or Targeting Pack for this framework version or retarget your
application to a version of the framework for which you have the SDK
or Targeting Pack installed.
XamlCompiler error WMC1006: Cannot
resolve Assembly or Windows Metadata file 'System.Runtime.dll'
Xaml Internal Error error WMC9999: Type universe cannot resolve assembly:
System.Runtime, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a.
Obviously, copying and pasting stuff around is not a way to go. Is there some proper approach to achieve what I want?
EDIT: The build machine has Windows Server 2012 installed, not Windows 8.1. Could that be a problem?
EDIT 2: After comparing outputs of msbuilds executed both on development machine and build server, I've noticed that the folder C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETCore\v4.5.1 is missing from the build machine (there is only 4.5 folder). After pasting it, I got the following error:
CompileXaml error WMC9998: XBF generation failure due to missing
Windows 8.1 Support, Set property
<DisableXbfGeneration>true</DisableXbfGeneration> in your Project file
and try again.
There is still something missing from the Windows 8.1 toolchain...
Since it's a windows store app, and Windows Server 2012 doesn't have an app store, I'd say the libraries needed in order to compile the app are just missing from the OS itself. I suggest running tracer on a windows 8.1 box to see what files are accessed during compilation, and copy them to the server. I'm not certain that this will work, but it's the likeliest scenario I can think of. You can use something like Process Monitor for this
See what files/registry keys are being accessed by application in Windows
Alternatively, you might want to monitor the temporary build folder in .net to see what assemblies get copied locally during the build.
EDIT: Microsoft doesn't officially support this http://msdn.microsoft.com/en-us/library/windows/apps/br211384.aspx
Did you download and install Microsoft Build Tools 2013 on the build server? The v12 version of MsBuild is now released as part of Visual Studio (instead of the Microsoft.NET Framework) and you'd want to use this separate install to get the MsBuild v12 bits on your build server.
I just did this a few weeks ago for a Windows 8 store app so it should be the same for Windows 8.1. As long as the build machine is running Windows 8.1, All you should need to do is install the latest Visual Studio Express for Windows Store Apps on the build machine and you should be fine. It should install everything you need.

Could not load Microsoft.Build.dll in Windows Phone 8 SDK and VS 2012

I have installed the Windows Phone SDK 8.0 and Visual Studio 2012 Premium with Update 1. When I create now a new phone project I get three errors:
Error 1 The "CompileXaml" task could not be instantiated from
"C:\Program Files
(x86)\MSBuild\Microsoft\WindowsPhone\v8.0\Microsoft.Silverlight.WindowsPhone.Build.Tasks.dll".
Could not load file or assembly 'Microsoft.Build.dll' or one of its
dependencies. An attempt was made to load a program with an incorrect
format.
Error 2 The "CompileXaml" task has been declared or used incorrectly,
or failed during construction. Check the spelling of the task name and
the assembly name.
Error 3 The name "LocalizedStrings" does not exist in the namespace
"clr-namespace:PhoneApp24". C:\PhoneDevelopment\PhoneApp24\PhoneApp24\App.xaml
While googling I found some guys out there who have similar errors while using Windows 8 in a virtual machine. But in my case I have installed everything on my laptop. I have also already uninstalled VS2012 and the SDK. But after the reinstallation I still get the same exceptions.
Can someone please give me some hints?
This happened to me as well after trying to create a project using a VMWare shared folder for the file. Try creating the project in a local directory if you are using a VM then the project will build fine. Apparently the assembly files are either not downloaded properly or do not have permission to be read. More than likely it's the namespace itself causing the issue.
Error 1 Could not load the assembly file://\vmware-host\shared folders\Documents\Visual Studio 2012\Projects\NewApp.dll. This assembly may have been downloaded from the Web. If an assembly has been downloaded from the Web, it is flagged by Windows as being a Web file, even if it resides on the local computer. This may prevent it from being used in your project. You can change this designation by changing the file properties. Only unblock assemblies that you trust. See http://go.microsoft.com/fwlink/?LinkId=179545 for more information.
Try running VS2012 as administrator.
After spending hours trying to get the sdk working I finally did a window recovery. Since windows 8 this is now a very quick process. Just insert the windows cd and run the setup again. If you choose the right option you can reinstall windows 8 without loosing your data. After 10 minutes your system reboots and you have to fill in again some data.
After that I installed the SDK. No error poped out and everything went very smoothly. Then I started VS express, created a project and built it successfully!
After the SDK installation I found two additional tiles on my desktop: "Hyper-V Manager" and "Hyper-V Virtual Machine...". I am pretty sure that those two tiles were not when I installed the SDK before. So I guess that I have had some problems with my virtual machine and that this was probably the source of the building exceptions.
I had this trying to run one of the Office 365 API samples and it turned out to be a missing file in the solution. Specifically, the solution was expecting a temp PFX certificate at the root of the project. I removed that and the build errors stopped.

Categories