60 Second Dev

The new way of writing tuples in C# is much nicer than the old Tuple class. Learn more with the Microsoft docs View code in GitHub

XmlWriter is an easy way to generate XML when you need it. If you're building something more complex, like something for an API, you probably want to go with serialization instead. Otherwise, this is pretty easy to build XML how you want it top to bottom. View code on GitHub

When looking up data in memory from a large collection, a HashSet or Dictionary is much, much faster than looping through an ordinary collection. This example uses strings - if you run the same code but treat them as GUIDs, the numbers improve quite a bit, but the difference between array and HashSet is still tremendous. View code on GitHub

private static SqlDataRecord CreatePersonRecord ( int id , string name ) { var metaData = new [ ] { new SqlMetaData ( " Id " , SqlDbType . Int ) , new SqlMetaData ( " Name " , SqlDbType . VarChar , 50 ) } ; var record = new SqlDataRecord ( metaData ) ; record . SetInt32 ( 0 , id ) ; record . SetString ( 1 , name ) ; return record ; } private SqlDataRecord [ ] GetPersonRecords ( ) { retun new [ ] { CreatePersonRecord ( 1 , " John Doe " ) , CreatePersonRecord ( 2 , " Jane Doe " ) } ; } using ( var conn = new SqlConnection ( cs ) ) { conn . Open ( ) ; using ( var comm = conn . CreateCommand ( ) ) { comm . CommandText = " dbo.TestPerson " ; comm . CommandType = CommandType . StoredProcedure ; var peopleParmsValue = GetPersonRecords ( ) ; if ( ! peopleParmsValue . Any ( )

 If you're working locally, building a new app from scratch, you might be in a position where you want to wipe the database and start clean – but SQL Server may block you if you've got any open connections or any other issues blocking you. This should set you as the only user of the database, which will clear the way for dropping it without ever getting an error: use master ; go if exists ( select 1 from sys . databases where name = 'SomeDatabase' ) begin alter database SomeDatabase set single_user with rollback immediate ; drop database SomeDatabase ; end ; go View code on GitHub

Consider using Identity , Google , domain authentication , or some other solution for authentication, rather than building your own username/password database. But, if you are doing it anyway, here's some code to get you started: View code on GitHub