ICaramba

Miguel Castro's blog about .NET and its effect on National Security, the Eco-system, and his daughter's sleeping patterns.


News

My Stats

  • Posts - 120
  • Comments - 69
  • Trackbacks - 145

Twitter












Recent Comments


Recent Posts


Archives


Image Galleries



Blogs I read


Links


Microsoft DCCs


September 2007 Entries

Compiling apps under Vista 64


I just loaded the code for CodeBreeze (which you can learn all about in episode 77 of www.dnrtv.com and obtain at www.steelbluesolutions.com) and I came into a small problem.

CodeBreeze (which you can learn all about in episode 77 of www.dnrtv.com and obtain at www.steelbluesolutions.com) uses a licensing program from Interactive Studios, called QLM (www.interactive-studios.com).  The component that it uses from this product is a .NET component but it calls an unmanaged DLL which can only run in 32bit.  The problem was that I was compiling CodeBreeze (which you can learn all about in episode 77 of www.dnrtv.com and obtain at www.steelbluesolutions.com) to target .NET 2.0 and "Any CPU".  This was causing a nasty error.

The solution was to target "x86".  Now it works fine, even in Vista 64 which is what I'm running.

That's fine anyway cause CodeBreeze (which you can learn all about in episode 77 of www.dnrtv.com and obtain at www.steelbluesolutions.com) is not a 64 bit app.

If you develop commercial software, you really want to check out QLM at www.interactive-studios.com.  It has registration, activation, custom feature, and a full API at your disposal.

And don't forget to checkout CodeBreeze (which you can learn all about in episode 77 of www.dnrtv.com and obtain at www.steelbluesolutions.com).

posted @ Wednesday, September 26, 2007 4:01 AM | Feedback (6) |


Something interesting (and annoying) in VS2008


I started using nested Master Pages in Orcas last week and ran into a small snag.  I could not get a break point to fire on the Page_Load in the child Master Page's code-behind class.  In fact I noticed that the code wasn't running at all.  After 30 minutes of beating my head against the wall, I tried changing the Page_Load method to an override of OnLoad and that worked perfectly.  Then it ocurred to me to check the AutoEventWireup value in the Page directive and sure enough it was set to False.  This is the first situation I've seen where it does not default to True so if you come across this, jump straight there and you should find the problem.

posted @ Monday, September 10, 2007 11:13 AM | Feedback (1) |