Microsoft DevDays ‘09, I’m attending!

Thanks to our friends at Microsoft (and their great BizSpark program) I will be able to attend DevDays ‘09! We won tickets because we updated our company profile and added projects at the Discover Metro site. Normally attending this kind of event is not available to young startups like ours, but now it is!

I’ll be seeing you @ The Hague next week :)

Finally, a way to preview your site in all (important) browsers

I just read this great article by Mark Voermans: Expression Web SuperPreview: Look how your site renders in various Browsers

I don’t know about you guys, but I’ve been waiting for this for a long, LONG time. I’ll give it a go this afternoon and let you know what I think…

Update
This first beta version only allows you to preview your site in different versions of Internet Explorer. We will have to wait for the full feature set until the final release of this tool…

Taken from the SuperPreview site:

This free download will allow you to compare renderings of IE6 with whatever other version of IE you have installed on your machine. If you have installed IE8, you’ll be able to compare IE6, IE8 and IE8 running in IE7 compatibility mode, side-by-side.

Fix available for IE8 asp:menu problem

I just read an interesting article on Bertrand Le Roy’s blog. The most important information:

It so happens that the menu control is making a bad assumption on what the default value for z-index should be. We debated this at length with the IE team, but it became clear as we did so that they were right and that we were wrong. We had to fix that.

So here it is, the patch for menu is out and you can apply it to build IE8-compatible ASP.NET WebForms sites…

Windows 2000, XP, Server 2003:
http://code.msdn.microsoft.com/KB962351/Release/ProjectReleases.aspx?ReleaseId=2294

Windows Vista, Server 2008:
http://code.msdn.microsoft.com/KB967535/Release/ProjectReleases.aspx?ReleaseId=2328

(the KB article is not yet ready but will be published shortly)

Read the entire article over here: http://weblogs.asp.net/bleroy/archive/2009/03/23/asp-menu-fix-for-ie8-problem-available.aspx

In this mode, command line arguments will not be passed to the executable

When trying to pass some command line arguments to a Console Application, I got the following message: “The current project settings specify that the project will be debugged with specific security permissions. In this mode, command line arguments will not be passed to the executable. Do you want to continue debugging anyway?” (see image)

The current project settings specify that the project will be debugged with specific security permissions.  In this mode, command line arguments will not be passed to the executable.  Do you want to continue debugging anyway? 

I didn’t run in to this earlier, but yesterday it suddenly popped up. But I did change my zone security, so that might be of some influence… Apparently, this is because of the Debug in Zone settings you can find at the Security tab of your project properties. Deselecting the ‘Enable ClickOnce Security Settings’ checkbox will solve this ‘problem’ for you.

For more information about Code Access Security, take a look over here: http://msdn.microsoft.com/en-us/library/z17ceyya.aspx

Installing my laptop after a repair

I’m reinstalling my laptop after I got it back from a repair… EMPTY (grrr).

What tools shouldn’t I forget when preparing this laptop to be my development machine? Already have Visual Studio, SQL Management Studio, Office and the Windows Live tools installed… (and of course I have all kinds of tools at hand from my server like DebugView, Reflector and whatnot)

Clicking ‘Choose items’ on the toolbox crashes Visual Studio 2008

I’ve had my current installation for a few months now, and I’ve used it for development purposes. Today I suddenly encountered an error when trying to add items to the Toolbox. Visual Studio 2008 simply disappeared… No errors, no warnings, it just went away.

After some searching and a lot of trying, I found that deinstalling the PowerCommands for Visual Studio 2008 did the trick. I’m guessing that the installation of a service pack (for either Visual Studio or .NET Framework) changed something somewhere, making Visual Studio disappear into thin air when having PowerCommands installed and clicking the ‘Choose items’ context menuitem. Anyway: the problem is gone now…!

According to some forumposts I read reinstalling the PowerCommands after this problem was solved does not cause the problem to reappear. I haven’t come to testing that yet ’cause I’m working on a deadline here… (Why do these things always happen when you have a deadline…?)

Hope this helps.

Nice new addition to ASP.NET

Scott Guthrie posted about a cool new ASP.NET server control: Chart. It can be used for free with ASP.NET 3.5 to enable rich browser-based charting scenarios.

Read more over here: http://weblogs.asp.net/scottgu/archive/2008/11/24/new-asp-net-charting-control-lt-asp-chart-runat-quot-server-quot-gt.aspx

Inline wrappers & Response.Redirect() == Error

While developing a page that was to be used through an inline wrapper, I got an error: “Validation of viewstate MAC failed”. This error can usually be resolved by disabling event validation, viewstate encryption or viewstate for the MAC. In my case these solutions did not resolve the issue.

After some testing Response.Redirect appeared to be the cause. I changed the page so it doesn’t need the redirect any more, and the problem disappeared. I’ll try if ending the response when redirecting will help, but for now I can continue working…

Hope this helps.

An inline wrapper and having too much on your head

We developed an ASP.NET page (A) to be wrapped in an existing PHP page (B) using an inline wrapper. After a few days in which both pages displayed nicely, our page (A) suddenly got displayed twice inside the existing page (B).  And even weirder was that the postbacks of the first occurrence didn’t work, and the postbacks of the second were executed outside of the wrapper.

We had changed some stuff the night before, so I finally checked the file line by line against an earlier version. The problem we eventually found was small and not too easy to find. But so easy to solve… Because of an external editor, the page’s (A) header had received an ID, probably because of the runat=”server” tag. Removing the ID tag was enough to have both pages working fine again.

StyleCop v4.3 now available

StyleCop version 4.3 was released last tuesday. A short summary of what version 4.3 brings us: 

  • Various bugfixes, including fixes for VS integration issues
  • Rules documentation is included and integrated into VS “Show Error Help”
  • New rules, see blogpost for the rules
  • Branding change from Source Analysis to StyleCop

    Links
    StyleCop blog: http://blogs.msdn.com/sourceanalysis/
    Release announcement on the StyleCop blog: http://blogs.msdn.com/sourceanalysis/archive/2008/08/19/stylecop-4-3-is-released.aspx
    StyleCop 4.3 download: http://code.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=sourceanalysis&ReleaseId=1425