Posts Tagged ‘’ WebPartZone skins and CSS

I was just examining a MonoX portal skin that our designer is authoring for the ClipFlair platform and noticed that in the file, there’s a note pointing to that speaks of an issue with Microsoft’s implementation of WebPartZone skins:

There it says:

The CssClass property does not affect the following style objects:

•The MenuLabelHoverStyle property
•The MenuPopupStyle property
•The MenuVerbHoverStyle property
•The MenuVerbStyle property
•The MenuCheckImageStyle property

Do not use the following line of code:

<MenuPopupStyle CssClass="wp_menupopup" />

while having a Stylesheet.css file with the following code:


Instead, use the following line of code:

<MenuPopupStyle backcolor="red" />

In short, at the file one can give a CssClass and then define the styles at Stylesheet.css, but for MenuPopupStyle, MenuVerbHoverStyle, MenuVerbStyle and MenuCheckImageStyle this doesn’t work and you have to enter the object properties that correspond to the CSS attributes you want (e.g. background property of for the background-color CSS attribute) directly into the file for the respective objects.

BTW, the aformentioned Microsoft article speaks of Stylesheet.css, while MonoX template uses Default.css. This is because the theming engine applies all .css files it finds in the theme folder (independent of filename), as explained at That last Microsoft article has lots of useful information regarding Themes and how you can (optionally) combine them with CSS and on issues like scoping, precedence, security etc.

Converting a VB6 form to an WebForm

See my opensource VB6toWebForm tool at

It converts a VB6 form’s design to XML (eXtended Markup Language) via my VB6FormDesignToXML tool that you can also find on that site, and then via XSL (eXtended Stylesheet Transformations) it converts that XML into 1.x WebForm pages (using classic vertical flow layout based on the tab-order from the VB6 form and making sure labels that have been assigned to edit controls stay on the same line as those controls)

If you use 2.x, has a nice import wizard (which won’t convert the coding style of those 1.x pages [e.g. the usage of a single codebehind file without using a partial class – a concept that .NET1.x didn’t support], but will tweak them to work fine with 2.x)

If you add to the XSL transformations files logic to handle more VB6 controls, please consider contributing your enhancements to the tranXform project

BTW, more free XML related utilities are on that website



if you get a transformation error, please open up WebForm.xsl in XSL subfolder and replace | with or (with small letters). Seems MSXML engine stopped supporting | in test expressions and needs or instead. However, better download the latest version from that now also supports MDI forms etc.

Categories: Posts Tags:

web.config’s schema change at .NET2: node doesn’t define child node anymore

At an project I was moving from 1 to 2, at "web.config" file of the web application I had to move <compilers> child node of <configuration>/<system.web>/<compilation> node to a new <configuration>/<system.codedom> node.

The former one has been deprected at .NET2 (although still supported and overriding the <system.codedom>’s <compilers> setting if existing) and the Web.config XML editor was compilaing that the schema didn’t define a <compilers> child for <configuration>/<system.web>/<compilation> node.

Categories: Uncategorized Tags:
%d bloggers like this: