MS D3D and vb.net tech chat comming up

MS is holding a tech chat for VB.NET and D3D! on march 30th. Here are the details ...

Do you have questions about how to best use Visual Basic .NET to program DirectX 9.0 graphics? Are you unsure when to use a particular Direct3D feature? Join members of the Visual Basic and Windows Graphics & Gaming Technologies teams and discuss how to leverage the power of DirectX 9.0 from Visual Basic.

Here is the link...
http://msdn.microsoft.com/chats/#vs_dirx0330

New code snippet!

Added new code snippet to code snips category called RWTextFile that contains 2 methods for reading and writing to a text file in one line of code!

Added a new code snip!

I have added a new code snip for capturing screen shots of your directx app! There are two easy methods you can use to take screen shots of your DirectX app!
CaptureScreenshot.zip

I just created a new app called ZipThatSnip

I am going to be creating a new category on the side bar called "Code Snips". This is where I will be placing a number of code snips that I think people may find handy. The problem is that I did not want to have to go through the hassle of creating a code snippet all the time and zipping the files etc, so I created a simple app to do just that.

ZipThatSnip is an app that allows developers to quickly make and zip code snips by selecting there code on screen and running the "ZipThat Snip" Macro that is provided.

For installation instructions and requirements click here.

ZipThatSnip.zip

Strange vs2k2 error and how to fix it.

Warrning to vs.net developers! I was just working in the vs.net 2002 forms designer and started getting the fallowing error...



... I could not figure out why I was suddenly getting this error seemingly out of no where.

Be carfull about adding this reference "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\" or one similar to it, under your Project property Pages ("Reference Path").

If I had to guess as to why adding this reference path in a vs.net 2002 project would cause the forms designer for that project to crash, I'd guess it would have somthing to do with vs.net 2002 using ver 1.0 of the .NET Framework rather than ver 1.1. Or possibly some sort of conflict there of.