We Keep Coding

VS Code doesn't recognise "using UnityEngine" as a valid namespace. What can I do?

I opened the ".cs" file from Unity after creating a C# file in my project, however
neither UnityEngine nor (obviously) MonoBehaviour is detected in VS Code.Due to this, Intellisense also can't help, which is a major obsticle for me, because I am completely new to the UnityEngine library. The OmniSharp log also gives a
warning in the output:
[fail]: OmniSharp.MSBuild.ProjectManager
Attempted to update project that is not loaded: c:\Users\bomka\My project\Assembly-CSharp.csproj
[warn]: OmniSharp.Roslyn.CSharp.Services.InlayHints.InlayHintService
Inlay hints requested for document not in workspace Location { FileName = c:\Users\bomka\My project\Assets\scripts\Circle.cs, Range = Range { Start = Point { Line = 0, Column = 0 }, End = Point { Line = 19, Column = 0 } } }
Things I've tried so far:
I've redownloaded both Unity and VS Code (latest versions, which are 2021.3.3f1 and 1.67.2, respectively)
I checked whether Visual Studio Code Editor and Visual Studio Editor were downloaded in Unity's Package Library (they are, it's 1.2.5 and and 2.0.15, respectively)
I changed omnisharp.path to "latest" in VS Code because I've read it resolved the "Attempted to update project..." issue. It didn't really do anything unfortunately
Does anyone have any ideas concerning what I should do here? Another useful piece of information is that this is my first ever Unity Project and so VS Code didn't just decide to malfunction after a while, this is how it's been behaving since I started writing my first piece of code for my project.
Cheers!

Is VS set in your external tools in Unity?
Edit > Pref > External Tools > External (Script) Editor : Visual Studio..
Not sure if it'll help but I know the above will fix Intellisense issues so it might be worth a shot.

Changing assemblyVersion adds version to Application.LoadComponent causing compile errors

I have a C# WPF application. It uses a small commercial framework (https://www.inosoft.com/en/product/product-features/).
I'm building this application both locally and via a buildserver (Azure pipelines). I use a marketplace task to change the assemblyinfo.cs before building: https://marketplace.visualstudio.com/items?itemName=bleddynrichards.Assembly-Info-Task
The build server executes the following tasks:
NuGet restore
Inject/Edit assemblyVersion, AssemblyFileVersion and AssemblyInformationalVersion with the right version info
Build
Now when I run this application, it starts up and runs for a while.
Quickly after starting I hook the VS debugger into the process.
Then all of the sudden the application crashes:
This is weird, because when I build locally, this runtime error does not occur.
Note that i set all properties to the same values for testing:
AssemblyVersion: 1.2.3.4
AssemblyFileVersion: 5.6.7.8
AssemblyInformationalVersion: 9.10.11.12
I then use Telerik justAssembly to compare the build output from my local build and the buildserver:
As we can see the local output (on the left) does not have a version added to the Application.LoadComponent(..) whilst the build server output (on the right) does.
public void InitializeComponent()
{
if (!this._contentLoaded)
{
this._contentLoaded = true;
Application.LoadComponent(this, new Uri("/HmiMetis;component/views/app.xaml", UriKind.Relative));
}
}
This means that this is the root cause of the runtime exception.
I find it weird that the build process on my local machine differs from the build server output. Both (should) use visual studio 2017 to build. Why does the buildserver add the version to the uri of loadComponent and my local machine does not?
Anyways, I need this exception gone.
Therefore I think the easiest way would be to force the buildserver to not add the version information under any circumstances. Is this possible and how?
Edit:
I Found a relating issue report that may have something to do with this:
https://github.com/dotnet/core/issues/3189

Mobile Center UITest exit code 20

I've been trying to run a UI test via Visual Studio Mobile center for a while now, but I'm getting the following error:
Preparing tests... failed.
Error: Cannot prepare UI Test artifacts. Returning exit code 20.
I looked on the mobile-center-cli github page and found that error codes 1 until 63 are reserved for TestCloud. There is really no documentation about this error so I hope someone is able to point me into the right direction.
Command used:
mobile-center test run uitest --app "MyAppName" --devices d5c95903 --app-path "pathToApk" --test-series "master" --locale "en_US" --build-dir "PathToBinRelease"

It sounds like you may be specifying the wrong folder for your --build-dir.
The --build-dir should be the bin/Debug folder of your Xamarin.UITest project, something like this:
"/Users/User/AppSolution/App.UITests/bin/Debug"
Can you please try the above and let me know if it resolves the issue?
Glenn

Another reason for this error is if there is more than one version of Xamarin.UITest present in the packages folder, that is visible in the root of your project.
Remove the unnecessary versions of Xamarin.UITest and give it another go.

I had this error. I added this param to my script:
--uitest-tools-dir "...your_path\packages\Xamarin.UITest.2.0.10\tools"
This is work for me.

--uitest-tools-dir $APPCENTER_SOURCE_DIRECTORY/packages/Xamarin.UITest.*/tools
https://tomsoderling.github.io/AppCenter-Automated-UI-tests-on-build/

Compile ASP.NET MVC Project in VS2013 doesn't work in release

I tried to compile my ASP.NET c# project with VS 2013 in Release mode but I can't do this. During the compile process I obtain some error like that one
Error 55 Could not copy
"\192.168.1.103\d$\ShareDLL\CommonTools\CommonTools20\CommonTools20.dll" to
"\192.168.1.103l\d$\ShareDLL\IndexCalculation\IndexCalculation\CommonTools20.dll".
Exceeded retry count of 10. Failed.
and then
Error 56 Unable to copy file
"\192.168.1.103\d$\ShareDLL\CommonTools\CommonTools20\CommonTools20.dll" to
"\192.168.1.103l\d$\ShareDLL\IndexCalculation\IndexCalculation\CommonTools20.dll".
Impossibile trovare il percorso di rete.
for some libraries.
The problem is that if I compile the same project in Debug mode everything works fine.
I have to set something in VS?
Thanks

I always resolve it like this:
1.Clean Solution (and do nothing else)
2.Close all open documents/files in the solution
3.Exit VS
4.Run VS
5.Build Solution
Dont know why it work, but work. (VS 2013 also)

Windows store app fails AppContainerCheck

I'm getting the below error when I try to run the app certification test on my windows 8.1 app. I've looked around for a while and can't seem to find any solutions for this. The app is written in C#/xaml which I wasn't aware even had a linker.
I'm hoping that someone can guide me in the right direction on how I should start to investigate an error like this as web searches have thus far failed me
Binary analyzer
•Error Found: The binary analyzer test detected the following errors:
◦File [MyTabletApplication.exe] has failed the AppContainerCheck check.
•Impact if not fixed: If the app doesn’t use the available Windows protections, it can increase the vulnerability of the customer's computer to malware.
•How to fix: Apply the required linker options - SAFESEH, DYNAMICBASE, NXCOMPAT, and APPCONTAINER - when you link the app. See links below for more information:

If you are using Visual Studio 2015 and this is a new solution/project make sure the 'Compile with .NET Native tool chain' check box is cleared in the startup project properties in the Release configuration.