The World of .NET covers practical .NET enterprise application development.
In this segment, we discuss Visual Studio Visualizers, a dialog box or other interface to display appropriate types in a meaningful way.
Default visualizers
Out of the box, Visual Studio provides the following visualizers:- Text- HTML- XML visualizer- Dataset visualizer (Dataset, DataTable and DataView objects.)
3rd party visualizers
Some useful 3rd party visualizers include Mole, Xml Visualizer, and Zeta Color Visualizer
To deploy/install 3rd party visualizers, copy the .DLL(s) to one of the following directories:\Install path\Microsoft Visual Studio 9\Common7\Packages\Debugger\Visualizers\—or—\My Documents\Visual Studio 2008\Visualizers\
Although the ASP.NET worker process (aspnet_wp.exe) defaults to Automatic: T-SQL code, Managed code debug types, you can change or add to the debug types by simply clicking on the [Select] button when attaching to the process. A handy usage would be debugging script.
Please join Mike Benkovich, of Microsoft, and myself as we discuss Practical MVC on BenkoTips Live.
For more information and to register online, go to http://www.tinyurl.com/practicalmvcpresentation
In this segment, we discuss jQuery, a JavaScript library with Microsoft backing, integrated into MVC and VS 2010.
jQuery and Visual Studio 2008:
To get up and running with jQuery, including IntelliSense, you need to first apply a Service Pack and also include a vsdoc JavaScript file that provides method/property/parameter information. KB958502 - JScript Editor support for “-vsdoc.js” IntelliSense doc Latest jQuery and vsdoc files More information surrounding the vsdoc fix Learning jQuery jQuery Reference
Glimmer - Wizard style jQuery code generation for image sequencing, drop down menus, and animation.
Coupling at the assembly level The higher the coupling is, the more painful maintaining your application will be. Metrics: Afferent coupling - types that depend on your assebly Efferent coupling - types inside your assembly that depend on outside assemblies
In this segment, we discuss Inversion of Control / Dependency Injection with an IoC tool. During the conversation, mention was made of Bob Martin’s SOLID principles, which include the Dependency Inversion Principle (pdf).
Some IoC tools: StructureMap Castle Windsor Microsoft Unity Ninject
We discuss a practice of class design which is to either provide an interface for a class or mark all public members as virtual. By following this practice by default, we can provide extensibility to our application. This can facilitate many pattern implementations and mock/stub testing frameworks.
ProcessExplorer and FileMon from the Windows SysInternals suite. While these tools aren’t necessarily targeted at developers, they’re great in troubleshooting situations.
We discussed several aspects of creating ASP.NET Web Forms server controls. We also mentioned that using .NET Reflector to examine Microsoft-provided server controls is a great way to see how they are constructed.
MSDN link on creating custom server controls: http://msdn.microsoft.com/en-us/library/aa530982.aspx
MSDN link describing all the metadata attributes for custom server controls: http://msdn.microsoft.com/en-us/library/ms178658.aspx
Treat Visual Studio compiler warnings as compiler errors – fix them before check-in.
Stack Overflow – a great site for getting answers to any of your programming questions.
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.