October 2005 - Posts
Marty Wasznicky posts about a tool that helps deal with Gac registration in Bts farms and checking versions, etc. Allows "group" management instead of machine management fo Assemblies.
BizTalk Assembly Replication and Viewer
Need to tools like this!
I want to teach a friend everything I know about HTML Production work (which won’t take long). By production work, I mean the process of receiving a Photoshop file, cutting it up, and producing nice clean semantic (X)HTML and CSS.
I’m not a master of such things (though I am pretty handy with CSS these days), but I do know there’s a difference in producing HTML for a static web page verse producing HTML for a dynamically rendered page such as an ASP.NET page. It’s those details that I feel I can teach her well that you don’t learn at many design shops.
"How would you like to triple the battery life of your laptop, tablet pc, iPod or portable DVD player -- without ever changing your current battery?"
Good site on tips for Microsoft Sql Server Performance articles:
Sql Server Performance
I haven't personally looked at the code ** yet **, but investigating it's use for a collaboration on a project. Looked at DotNetNuke (smooth platform if you ask me - can't comment on the coding).
But, www.FlexWiki.com get's a ding here:
Update 10/10/2005: Just took a long look at the FlexWiki code - MAN IT IS CRAP!!!!!
CSAH 1.2.4 allows you to copy single-byte, double-byte, and Unicode characters from VS.NET. Previous versions only allowed you to copy single-byte and Unicode characters, and converted multi-byte characters to question marks. The new version should work properly for any DBCS codepage. Much of the credit for the new version goes to Qingbo Zhou for his suggestions, help debugging, and testing.
Visual Studio .NET 2003 Automation Samples
Microsoft has invested heavily in Visual Studio .NET extensibility. This is an important part of Visual Studio .NET because it lets customers easily tailor the tool to their personal working style and enables them to accommodate team practices. You can simply capture several steps in a regular process (for example, for check-ins, creating new projects or forms, or updating code) and make that process available as a single command to invoke. Independent software vendors (ISVs) can implement entirely new features (including groupware, profiling tools, work flow, or life-cycle tools) that fit into Visual Studio .NET 2003 as seamlessly as if they were built into the shipping Visual Studio .NET product.
These code samples show you how to build VSMacros projects, add–ins, and wizards to make your teams more productive and to bend Visual Studio .NET 2003 to the ways you like to work. Look for more samples, as well as some white papers and overview documents, in the future.
All of these samples use the Visual Studio automation model, which is free and publicly distributed with Visual Studio .NET 2003. The Visual Studio .NET automation model is four to five times richer and more powerful than any automation model that shipped with a previous version of Visual Studio. With this new automation model, you can do the following:
- Intercept commands when they are invoked, and either provide preprocessing or implement the command yourself.
- Control the solution, projects, and project items by adding or removing them.
- Control the build configurations mechanisms and hook various build events.
- Control a large portion of the text editor.
- Implement commands that help you debug with the debugger objects.
- Control the Windows Forms Designer more easily and with more power than with what Visual Basic 6.0 offered over the Visual Basic Forms Designer.
- Create tool windows that behave just like the built-in tool windows for docking and floating.
- Provide content to the Property Browser when items are selected in tool windows.
- Control several of the built-in tool windows (including Task List, Toolbox, Command Window, and Output Window).
Seems that SEHExceptions keep showing up in various applications that I've seen over the past.
Here's some great tips on addressing with EnableVisualStyles; manifest files that help link to the proper version Common Controls (comctl32.dll) are one way but not the only way.
Include a call to Application.DoEvents() before Application.Run().
Move the erring code (that causes handle creation to happen) from InitializeComponent to the Form's Load method.
Use a manifest!
If using a manifest, the following is the format - change for you app as needed:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">