Visual Studio – Trigger a xUnit test run after project build event

To trigger a xUnit test run after a successful build,
add this to the project “Build Events” / “Post-build event command line:”

(You need xUnit runner console nuget package installed for this, above is for the 2.2.0 version).
Will produce something similar to this in the Output window “Build”:

Docs:
https://xunit.github.io/docs/getting-started-desktop.html#run-tests

How do I get NuGet to re-install/update all the packages in the packages.config?

Reinstall all packages in project:
Update-Package -reinstall -Project YourProjectName
Reinstall package “Antlr” in project:
Update-Package -reinstall Antlr -Project YourProjectName

See more here:

The following command will update all packages in every project to the latest version available from nuget.org.
Update-Package
You can also restrict this down to one project.
Update-Package -Project YourProjectName
If you want to reinstall the packages to the same versions as were previously installed then you can use the -reinstall argument with Update-Package command.
Update-Package -reinstall
You can also restrict this down to one project.
Update-Package -reinstall -Project YourProjectName
The -reinstall option will first uninstall and then install the package back again into a project.
Or, you can update the packages using the Manage Packages dialog.

Source: How do I get NuGet to install/update all the packages in the packages.config? – Stack Overflow

 

ASP.NET / .NET / VS blogs to follow

Microsoft Official

.NET Web Development and Tools Blog | Your official information source from the .NET Web Development and Tools group at Microsoft.
RSS: https://blogs.msdn.microsoft.com/webdev/feed

The Visual Studio Blog | The official source of product insight from the Visual Studio Engineering Team
RSS: https://blogs.msdn.microsoft.com/visualstudio/feed/

.NET Blog | A first-hand look from the .NET engineering teams
RSS: https://blogs.msdn.microsoft.com/dotnet/feed/

Non Microsoft

Dot Net Weekly:
http://www.dotnetweekly.com/
RSS: http://www.dotnetweekly.com/feed/

PetaPoco – lightweight .NET ORM

This one looks like a great .NET lightweight ORM:

PetaPocoA tiny ORM-ish thing for your POCOsPetaPocoMainDocumentationLicensePetaPoco is a tiny, fast, single-file micro-ORM for .NET and Mono.Like Massive it’s a single file that you easily add to any projectUnlike Massive it works with strongly typed POCO’sLike Massive, it now also supports dynamic Expandos too – read moreLike ActiveRecord, it supports a close relationship between object and database tableLike SubSonic, it supports generation of poco classes with T4 templatesLike Dapper, it’s fast because it uses dynamic method generation (MSIL) to assign column values to properties

Source: PetaPoco – Topten Software

C# Interactive Window · Wiki doc

The C# Interactive Window provides a fast and iterative way to learn APIs, experiment with code snippets, and test methods by giving immediate feedback on what an expression will return or what an API call does.

The C# Interactive Window is a read-eval-print-loop (REPL) with advanced editor support. It supports features like IntelliSense as well as the ability to redefine functions & classes. After entering a code snippet–which can contain class and function definitions at top-level along with statements–the code executes directly. This means you no longer need to open a project, define a namespace, define a Main method, add a Console.WriteLine() call to output your result, and add a Console.ReadLine() call in order to play with code. In other words, say goodbye to ConsoleApp137 or whatever ridiculously high number your Console Apps default to today!

Source: Interactive Window · dotnet/roslyn Wiki · GitHub