Hello, I'm   Jason

Another thing Scott Guthrie pointed out to me is that in order to get the Theme and the stylesheet to work across the site in design mode, I must set both the theme and syleSheetTheme properties in the web.config file. Otherwise, it will not render in the designer. Again, another thing I just realized. I must have been setting this on each page in previous projects or ignored the designer and assumed that it wasn’t supported.

I asked the ASP.NET team a simple question: Why/How can I get the design view to work when I set the master page file in the web.config instead of the page level. Scott Guthrie replied back with a link that didn’t necessarily answer my question, but provided some good tips and tricks for Master Pages. In short, it doesn’t appear as though it can be done. This is something that might make the Orcas list. I can’t believe that in using this for the past 2 years that I haven’t noticed this.

Have you downloaded the Microsoft Expression Web Designer or CSS Control Adapters yet? If not, what are you waiting for? Many designers have argued that Microsoft does not support CSS throughout the design/dev tools and also with rendering the controls. Well, that’s no longer the case. You can now design using Microsoft Expression Web Designer using built-in CSS templates. You can also use CSS Control Adapters to convert the table-based controls such as menu and treeview to a CSS control.

Microsoft has been working with a few other companies creating a “Center for Information Work.” Here are some photos from CIW: http://www.microsoft.com/presspass/presskits/ciw/gallery.mspx. However, this week they released something even cooler. There is a new monitor that companies are developing to “wrap around” your workstation. Here is a picture from eWeek:

Scott Guthrie has just posted a cool tutorial on building a website using LINQ which can now be downloaded. If you haven’t downloaded LINQ yet to try it out, be sure to do so. LINQ will be fully integrated with the next version of Visual Studio.

I just noticed that Microsoft has released the first Community Technology Preview (CTP) for the Expression Web Designer. The Expression Web Designer allows designers to build standards-based Web sites, includes sophisticated CSS-based layouts, includes extensive CSS formatting and management, and provides rich data presentation. You can download it now and report any bugs to the team using http://connect.microsoft.com/.

Scott Watermasysk and Don Demsak (DonXML) are putting together the 2nd New Jersey Code Camp to be held at the Microsoft office in Iselin, NJ on Saturday, June 3rd. I spoke at their first code camp and unfortunately will not be able to make the trip for …

The .NET Valley User Group will be holding its next meeting on May 24th, 2006 in Scranton, Pennsylvania. More details will be available on the .NET Valley website at a later date.

In case you were unaware, any website using Flash or any other embedded object that interacts with the user will now prompt the user asking them to “Click to activate this control.” It seems as though its going to be a big pain. If anyone found a way to get around this (although I’m sure its a security risk), short of uninstalling the update, let me know.

Windows XP SP2 now provides more detailed error messages when processing unhandled exceptions. Yesterday I was rebuilding a VB6 application that would not error on 3 of our PCs, but would on others. I knew that the error message had to be something that would stick out like a sore thumb. The error message looked like this:

1
2
3
4
5
6
7
8
9
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="MyPrime.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="MyPrime.exe" SIZE="2510848" CHECKSUM="0x7605131D" BIN_FILE_VERSION="3.0.0.14" BIN_PRODUCT_VERSION="3.0.0.14" PRODUCT_VERSION="3.00.0014" COMPANY_NAME="United One Resources" PRODUCT_NAME="Real Estate Services Application" FILE_VERSION="3.00.0014" ORIGINAL_FILENAME="MyPrime.exe" INTERNAL_NAME="MyPrime" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x270F87" LINKER_VERSION="0x30000" UPTO_BIN_FILE_VERSION="3.0.0.14" UPTO_BIN_PRODUCT_VERSION="3.0.0.14" LINK_DATE="05/05/2006 16:10:08" UPTO_LINK_DATE="05/05/2006 16:10:08" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="983552" CHECKSUM="0x4CE79457" BIN_FILE_VERSION="5.1.2600.2180" BIN_PRODUCT_VERSION="5.1.2600.2180" PRODUCT_VERSION="5.1.2600.2180" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF848" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2180" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2180" LINK_DATE="08/04/2004 07:56:36" UPTO_LINK_DATE="08/04/2004 07:56:36" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

After doing some digging in the other applications, I was able to determine that the error surrounded the Adobe Type Library (Acrobat.tlb) version that was referenced in the application. On my PC, it was version 7.0 even though I had 5.0 and 7.0 installed. Once I changed the version and compiled, the other PCs with version 5.0 registered worked fine with no errors.

This was one of those things that you might not check if you only build every few months.