Hello, NuGet I find NuGet to be pretty awesome. Even though it’s several years old, it still has that new car smell to me. We recently started using the NuGet Package Restore feature, which has helped improve our CI builds. But like leather bucketseats, the feature I’ve wanted to have for a few years is … More Creating Your Own NuGet Package, Part 1
Automagically Using NuGet with a Project Want to automate things even more? For this example, find a Class Library project that you like. Open a command prompt and navigate to the folder where the .csproj file for that project is. nuget spec Bam. Now you have a .nuspec file created automatigically. You’ll notice some strings … More Creating Your Own NuGet Package, Part 2
If you use NuGet package sources, you will need to add a new package source to your preferences in Visual Studio. In VS 2012 and 2013, this is under Tools –> Options –> Library Package Manager –> Package Manager Settings –> Package Sources). If you want to try out a cool new trick: Ctrl + Q package sources … More Adding other NuGet Package Sources in Visual Studio
Setting Up Your NuGet Package Source Assuming this is for internal use only, your best bet is likely going to be creating an internal nuget server or creating a network share (the network share is considerably slower than the nuget server) to house all of your NuGet packages. If this is meant to be externally accessible, then you … More Setting Up Your NuGet Package Source
Improving unit testing, and use some sleek OOP too. Let’s say that we want to test a call to a basic stored procedure, where @ClientID is required. EXEC MYDB.MYSCHEMA.GetClients @ClientID = 10001 Now we want to test the database call in a unit test. If we don’t pass in @ClientID, we should expect a SqlException, … More Unit Testing: Using Extension Methods for better Exception Catching
