A little fresh on the C# train... so this may be a dumb question.
I have installed the WS3.0 SDK.
I have a website created in VS2013.
using Microsoft.Web.Services3;
Gives me "does not exist in namespace..." error.
Tried adding manually through Add>Reference, but it is not listed anywhere.
I can confirm that a file name Microsoft.Web.Services3 exists in Windows/assembly directory.
What am I missing?
I found it, in part thanks to #TimFreese.
Went to "Browse" in the reference manager, found the .dll hiding out in
C:\Program Files (x86)\Microsoft WSE\v3.0
Related
I have upgraded from 2018.3.14f to 2019.2.13 and I started having really strange errors.
I am now having those two errors:
The type or namespace name EventSystems' does not exist in the namespaceUnityEngine'. Are you missing an assembly reference?
and
The type or namespace name UI' does not exist in the namespaceUnityEngine'. Are you missing an assembly reference?
This is happening only to the project which I upgraded from 2018.3.14 to 2019.2.13.
If I create a new blank project with 2019 there is no issue. The namespaces are found plus when I go to New2019Project/Library/ScriptAssemblies/ I can see the following files:
Then If I go to my upgraded old project in this dir OldUpgradedTo2019Project/Library/ScriptAssemblies/ the folder is having only those files:
As you can see I don't have those files in my updated project. If I try to copy the ones from the new working one into my old upgraded, at the time I start the Unity for the upgraded old project it deletes them and the problem stays.
Is there any way I can fix this annoying problem?
What fixed this issue for me was to update to the latest 'Visual Studio Code Editor' in the Unity Package Manager. To do this, go to window -> package manager -> set 'All Packages' to 'In Project', select the Visual Studio Code Editor and update.
I was experiencing the same issue, but my problem was that I had multiple Google.VersionHandler.dll files in separate folders within Assets. As a result, the .asmdef files were not loading. Here's how I fixed it:
Close Unity and Visual Studio
Remove the extra copy of Google.VersionHandler.dll
Delete all .csproj and .sln files
Delete Library, obj, and Temp directories
Reopen Unity
Click Assets > Open C# Project to regenerate .csproj and .sln files
Hope this works for you!
I update my Visual Studio 2017 to Visual Studio 2019, then everything works.
Hope this works for you.
Yesterday, I have finished working on my Android project (c# and Xamarin) on Visual Studio 2017, I closed it. Today, I re-opened the project in order to continue my work but the project is not loading, plus, I am getting an error in the output window saying:
There is a missing project subtype.
Subtype: '{EFBA0AD7-5A72-4C68-AF49-83D382785DCF}' is unsupported by this installation.
I have searched up and tried every solution online but nothing worked for me. I tried to delete .suo file, repairing vs.. I do not know what to do.. please help me to solve my problem.
Here's a screenshot of the error
UPDATE
I enabled Xamarin for Visual Studio, now the error in the output window is (and the project is still failing to load):
[I:]: Found Xamarin.Android 8.0.0.33
[I:sdk]: Runtime path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Xamarin\Android
[I:sdk]: Framework path: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid\v1.0
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\AndroidSdkDirectory found:
Path contains adb in \platform-tools (C:\Program Files (x86)\Android\android-sdk).
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\AndroidNdkDirectory found:
Path contains ndk-stack in \. (C:\ProgramData\Microsoft\AndroidNDK64\android-ndk-r13b).
[I:sdk]: Key HKCU\SOFTWARE\Xamarin\VisualStudio\15.0_6c165955\Android\JavaSdkDirectory found:
Path contains jarsigner.exe in \bin (C:\Program Files\Java\jdk1.8.0_131).
[I:]: Found Android SDK. API levels: 22, 23, 24, 25
Never worked with XAMARIN before but faced somewhat similar situations with other projects. Here's what you can do :
1. Create a new project
2. Right click on project > Add > Existing Item
3. Browse to the previous projects directory and add all the project files(i mean code files such as .cs)
**4. In winforms, if you add back a form's .cs file, it should automatically load the .designer.cs as well. **
After doing so, you can get back the entire project. There might be a few errors but they are easily fixable.
Hope this helps :)
I had a global.json with and sdk for dotnet core that wasn't installed.
Either install the targeted version or update your global.json to fit what you have installed.
We are running the 'Welcome to Xamarin` example on Visual Studio Enterprise, using the latest Xamarin, in a Windows 8.1 environment.
We are managing to build and run on both Windows and Apple, but we are facing problems with Android.
Error:
The referenced component System.ObjectModel could not be found.
The errors can be seen in the screen shot below:
See screenshot
We've already tried searching online for solutions, we found some, which we tried, but to no avail.
On the other hand, is Xamarin compatible with Windows 8.1? Perhaps some Android requirement actually needs a Windows 10 environment.
Any help would be appreciated.
Right click on your Android project's references and manually add the reference: C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.ObjectModel.dll. And technically that's a warning, not an error.
I simply removed the reference entirely since none of my code actually used it.
In the Package manager console type: (Select the Android project)
update-package -reinstall
Is slower but is the correct method and always works
Exercise 1 from GitHub https://github.com/XamarinUniversity/XAM135/
when opening has the same problem.
Based on the above solutions I resolved by performing the following steps:
Update the Nuget Package
Save, close and abire the solution
Click on the Portable (shared) project-> Referencias-> Donet in the copy properties of the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111"
Open Windows Explorer and paste the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111", here is the System.ObjectModel.dll file
Click on the Droid Project -> Referencias and REMOVE System.ObjectModel
Right click on References and Add references
Click the Browse button and open the path = "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETPortable\v4.5\Profile\Profile111"
Select System.ObjectModel.dll, and then click Add and OK
The reference was added successfully! Save, compile the project.
Here is a similiar solution
Try moving it to desktop, then add it as ref in solution. worked for me, visual studio had access to all the other ref but for some reason dident have access to that specific ref. So i moved it, and i think it gave visual studio access. simply try to move it where access wont be a problem.
Copy dll and paste to packages folder. Change reference to new location and run project. Of course it's temporary solution. You can check another location for path without white spaces in folders name.
ovee
yes, you are partially correct, it works, but after again giving to old location (C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\ReferenceAssemblies\Microsoft\Framework\MonoAndroid\v1.0\Facades\System.ObjectModel.dll) missing error resolved.
So, I'm getting this not-so-rare error from what I have been able to search around for solutions:
Activation context generation failed for "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress.exe". Dependent Assembly debuggerproxy.dll,processorArchitecture="X86",type="win32",version="1.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
I get this btw when I try to start up my VS 2013 Express Win Desktop version.
I went into Computer->Manage->Win Logs->Apps and see a file called debuggerproxy.dll is missing. Well, I downloaded the file and copied into this location:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\WDExpress
but it didn't help.
Does anyone know where this file should be copied to?
Thanks...
I've searched everywhere and I can't seem to find anyone with the same problem (although I'm sure people have made the same mistake in the past)...I accidentally deleted the contents of my Debug and Release folders. Now I am getting file not found errors. As a background, it's a Windows Forms Application in C#, and I'm running Visual Studio 10.
Here's the errors:
Unable to read manifest 'bin\Debug\projectName.vshost.exe.manifest'
Could not find file [pathName]\projectName.vshost.exe.manifest.
Before I was missing the manifest, I was getting an error that it could not find the other contents of the folder (the exe, the pdb, etc.), error MSB3113 (link)
Things I've tried (and some of them were far-fetched, I know):
I tried renaming bogus files for all the missing files
I tried to find the deleted files, but can't
I tried deleting all the contents of the Debug/Release folders and doing a clean build
I tried deleting the Debug/Release directories
Let me know if you can think of anything I could try out. My issue seems to be vaguely similar to this one.
Here's how I ended up solving the problem - turns out I included my bin and obj directories in my project. For anyone experiencing the same problem, simply right click and "Exclude From Project." After doing this, clean and rebuild your project, and you should be good to go.
In my case the file app.manifest was checked-out. This file is located in my Winforms project under Properties folder. I selected this file from Pending Changes window and did "undo pending checkout". After that the build succeeded. This happened in Visual Studio 2008.
Worked for me: Properties => Build => Generate serialization assembly => change from Auto to Off