Welcome to MSDN Blogs Sign in | Join | Help

August 2004 - Posts

A few things that ASP.NET runtime supports while Visual Studio editor doesn't

There are a few features that are supported by ASP.NET runtime, but are not supported by Visual Studio Web forms editor. Therefore you do can create pages that will run just fine, but VS will refuse to provide intellisense or validation. Here is a list

Your product feedback votes at work

Last week a few DCRs (design change requests) have been approved the Visual Web Developer area for implementation in VS 2005 Beta 2. You may like the fact that 80% are based on the user feedback posted at MSDN Product Feedback Center . I implemented an

Adding custom DOM to the VS client script intellisense. Part 2: Events.

In my previous post I showed how to create a simple client script intellisense schema. I recei ved some feedback that this stuff is complex. Yes, I have to admit it might look scary. However, there are very few ways exist to describe objects, their methods

Adding custom DOM to the VS client script intellisense

Did you know that you can add your own document object model to Visual Studio client script intellisense? Here is how. The technique works in VS 2002 and VS 2003, but I will use VS 2005 for simplicity. In order to provide client script intellisense we

Why overflow:auto requires element to have fixed width or height?

While editing my Web site the other day I encountered an interesting problem. For some reason W3C decided that overlow property for some reason should only provide scroll if element has fixed size and/or absolutely positioned (I guess that's what is the

HTML editor based on Gecko

This weekend I downloaded NVU which is HTML editor based on Gecko engine.I played with a bit and quickly figure out that it exhibits the same problem as editor based on MSHTML: lack of preservation of user formatting and lack of XHTML compliance. Which

How do you see markup syntax of ASP.NET controls with generics?

Reading this post made me thinking how exactly markup for a generic control should look like. It would be nice to have something that is SGML-compiliant syntax so we won't have to special case anything in our parser. For example < vc : SomeGenericControl

Naming conventions: I don't like camel and I do like Hungarian

This post made me thinking about naming convention in managed code. I tend to disagree with naming guidelines on MSDN since names in them sound names in a typeless language such as Javascript. Hungarian is still useful since it is about code readability

Using W3C DTDs for XHTML validation in Whidbey

There is good article on new XML tools in VS 2005. Our team used to own VS XML editor back in VS 2003, but now we concentrate on HTML ans ASP.NET. Whidbey XML editor is brand new code written in C# on top of VS native text editor by a different team.

ASP.NET 2.0 feature cuts

Shanku, our GPM, posted official ASP.NET 2.0 runtime feature cuts . You may expect corresponding feature cuts from tools. For example, ASIX file support will be removed as well as Device Customization toolbar and related features. Same information is

Weather Forecast ASP.NET user control

I am posting source code for the weather report control that I am using on my Web site. It looks like this: It fetches weather forecast data from a free XML Web service provided by US National Oceanic and Atmospheric Administration (NOAA). There is a

Why there is no charset property in ASPX pages

...or how HTML editor handles file encoding. First, Visual Studio is a Unicode application and actually even supports Unicode Surrogates Pairs . Most of Web pages, however, are not stored in Unicode. Therefore when opening a Web page VS has to figure

Compiler nanny, take 2.

I found a better way than to use a function which I described earlier . The drawback of the function was that in some cases it requred the function to exist even in retail bits. So, now I do static volatile bool s_fFalse = false; #define ASSERT(x) do
 
Page view tracker