Geeks With Blogs

News View David Douglass's profile on LinkedIn

My Presentations
David Douglass .NET on My Mind April 2006 Entries
Register and Unregister DLLs Easily
Using the Windows command prompt to register / unregister DLLs using regsvr32 isn't much fun. These steps will allow you to do this from Windows Explorer: Create a shortcut to regsvr32.exe and place it in your SendTo folder (e. g., C:\Documents and Settings\Administrator\Send... Create a similar shortcut in SendTo and add -u to the end of Target: The shortcuts will appear on your SendTo menu, just point at a DLL / OCX and Sent To register or unregister! For another approach to this see http://blogs.technet.com/jh... ......

Posted On Thursday, April 20, 2006 4:40 PM

Book Review: CLR via C#, by Jeffrey Richter
CLR via C# 5 stars (out of 5) At the heart of Microsoft .NET is the CLR. .NET development is primarily about directing the CLR. But how can you do that if you don't really know what the CLR is or what it can do? Most .NET programming books are language centric. The capabilities of the CLR are implied based on the description of the language. Jeffery Richter's book is CLR centric. It describes what the CLR can do and how it does it. C# is used to provide practical examples of how to direct the CLR. ......

Posted On Monday, April 17, 2006 3:54 AM

Adventures in Code Generation Land
In some situations it is helpful to maintain an XML document using a class that mimics the structure of the XML document. If the document has a schema there shouldn’t be any reason to code the class. If the schema is well written, then everything necessary to generate the class is in the schema. You could then write code along the lines of: MyDoc doc = new MyDoc(documentPath); doc.Collection["key"].Name = "Joe"; doc.Save(); There are 3 code generators I know of for generating these classes. ......

Posted On Friday, April 14, 2006 1:55 PM

Silence of the Remoting Server
Most developers instruct Visual Studio to make local copies of DLLs. Whenever Visual Studio can detect a dependency between an executable and a DLL, it will copy the DLL into the directory where the executable is written. But Visual Studio can’t always see the dependencies. The typical solution for this situation is to do the copy by some other means. If the copy gets forgotten, you’ll usually find out at runtime when the CLR throws an exception because it can’t locate the DLL. ......

Posted On Thursday, April 6, 2006 8:24 AM

Copyright © David Douglass | Powered by: GeeksWithBlogs.net