Did you try to give the full path of the command that is running in the pre- or post-build event command? I was getting the 9009 error due to a xcopy post-build event command in Visual Studio 2008. The command “xcopy.exe /Y C:\projectpath\project.config C:\compilepath\” exited with code 9009. But in my case it was also … Read more
Assuming you have a Request object available, you can use: string.Format(“{0}://{1}{2}”, Request.Url.Scheme, Request.Url.Authority, Url.Content(“~”)); If it’s not available, you can get to it via the context: var request = HttpContext.Current.Request
According to this post, it’s much better now: // pick out one album JObject jalbum = albums[0] as JObject; // Copy to a static Album instance Album album = jalbum.ToObject<Album>(); Documentation: Convert JSON to a Type
MSDN has the answer: Choosing Between Classes and Structures. Basically, that page gives you a 4-item checklist and says to use a class unless your type meets all of the criteria. Do not define a structure unless the type has all of the following characteristics: It logically represents a single value, similar to primitive types … Read more
In .NET prior to version 2.0, “” creates an object while string.Empty creates no objectref, which makes string.Empty more efficient. In version 2.0 and later of .NET, all occurrences of “” refer to the same string literal, which means “” is equivalent to .Empty, but still not as fast as .Length == 0. .Length == … Read more
Ctrl + – and the opposite Ctrl + Shift + -. Move cursor back (or forwards) to the last place it was. No more scrolling back or PgUp/PgDown to find out where you were. This switches open windows in Visual Studio: Ctrl + tab and the opposite Ctrl + Shift + tab
From the .NET blog Announcing .NET 2015 Preview: A New Era for .NET: .NET Core has two major components. It includes a small runtime that is built from the same codebase as the .NET Framework CLR. The .NET Core runtime includes the same GC and JIT (RyuJIT), but doesn’t include features like Application Domains or … Read more
In ASP.NET Core 3.1, there are 4 main ways to specify a custom port: Using command line arguments, by starting your .NET application with –urls=[url]: dotnet run –urls=http://localhost:5001/ Using appsettings.json, by adding a Urls node: { “Urls”: “http://localhost:5001” } Using environment variables, with ASPNETCORE_URLS=http://localhost:5001/. Using UseUrls(), if you prefer doing it programmatically: public static class … Read more
This warning means that two projects reference the same assembly (e.g. System.Windows.Forms) but the two projects require different versions. You have a few options: Recompile all projects to use the same versions (e.g. move all to .Net 3.5). This is the preferred option because all code is running with the versions of dependencies they were … Read more
As mentioned in the question’s comments, differing .NET Framework versions between the projects can cause this. Check your new project’s properties to ensure that a different default version isn’t being used.