Asp.net 4.0 has not been registered
I also fixed this issue by running aspnet_regiis -i using the visual studio command line tools as an administrator
I also fixed this issue by running aspnet_regiis -i using the visual studio command line tools as an administrator
There’s 3 approaches :). In NuGet 1.1 (The latest release) we’ve improved powershell pipelining so you can do this: Get-Project -All | Install-Package SomePackage That will install “SomePackage” into all of your projects. You can use wildcards to narrow down which projects: Get-Project Mvc* | Install-Package SomePackage That will use wildcard semantics (in this case, … Read more
Ctrl+, I’m surprised no one gave the right answer: Navigate To can show you a list of open files and lots more. http://weblogs.asp.net/scottgu/archive/2009/10/21/searching-and-navigating-code-in-vs-2010-vs-2010-and-net-4-0-series.aspx CTRL+COMMA is your friend.
Edit.LineDelete is the name of the command. By default it’s bound to Ctrl + Shift + L, but you can give it whatever you like in Tools | Options | Keyboard. Edit: Corrected default shortcut info.
Console.WriteLine writes your output to the console window opened by your application (think black window with white text that appears when you open the Command Prompt.) Try System.Diagnostics.Debug.WriteLine instead.
I’ve finally found the solution. Edit the .csproj file for the project in question. Delete the following lines of code: <PropertyGroup> <ManifestCertificateThumbprint>………..</ManifestCertificateThumbprint> </PropertyGroup> <PropertyGroup> <ManifestKeyFile>xxxxxxxx.pfx</ManifestKeyFile> </PropertyGroup> <PropertyGroup> <GenerateManifests>true</GenerateManifests> </PropertyGroup> <PropertyGroup> <SignManifests>false</SignManifests> </PropertyGroup>
To make assertions about collections, you should use CollectionAssert: CollectionAssert.AreEqual(expected, actual); List<T> doesn’t override Equals, so if Assert.AreEqual just calls Equals, it will end up using reference equality.
You can safely delete the .sdf file and ipch folder but you can also stop VS from putting those files in the project folder in the first place. (Useful if you have your source in an SVN or other synchronised folder, or if you store your project on a small volume like a USB stick … Read more
I got it mostly working without a custom msbuild script. Here are the relevant TeamCity build configuration settings: Artifact paths: %system.teamcity.build.workingDir%\MyProject\obj\Debug\Package\PackageTmp Type of runner: MSBuild (Runner for MSBuild files) Build file path: MyProject\MyProject.csproj Working directory: same as checkout directory MSBuild version: Microsoft .NET Framework 4.0 MSBuild ToolsVersion: 4.0 Run platform: x86 Targets: Package Command line … Read more
I found that if ProjectX referenced the abc.dll but didn’t directly use any of the types DEFINED in abc.dll, then abc.dll would NOT be copied to the main output folder. (It would be copied to the ProjectX output folder, to make it extra-confusing.) So, if you’re not explicitly using any of the types from abc.dll … Read more