Tips and Tricks – Show assembly version numbers in Windows Explorer

Sometimes you want a simple overview of all the assembly file version numbers in the bin folder in your ASP.NET project.

For example when doing an upgrade or a release.

Go to your bin folder -> show files as detailed list in windows explorer.

Right click on one of the columns:
ScreenShot715

Scroll down to file version, or just start typing file to jump fast.
Check “File version”

ScreenShot714

Tada!ScreenShot716

TroutZoom extension – syncs zoom level in vs2012 vs2013

Syncs zoom level across all windows in Visual Studio, works in vs2012 and vs2013

TroutZoom FreeThis extension manages the zoom levels for the code windows. When the zoom level is changed in one document, it gets changed for other open documents and any new documents that are opened.

via TroutZoom extension.

 

javascript – Window.onload vs document.ready ? – Stack Overflow

The ready event occurs after the HTML document has been loaded, while the onload event occurs later, when all content (e.g. images) also has been loaded.

The onload event is a standard event in the DOM, while the ready event is specific to jQuery. The purpose of the ready event is that it should occur as early as possible after the document has loaded, so that code that adds funcionality to the elements in the page doesn’t have to wait for all content to load.

via javascript – Window.onload vs document.ready ? – Stack Overflow.

EPiServer Commerce R2 SP1 available metatypes and their UI representations

List of Commerce meta properties types and their Commerce manager representation UI:ScreenShot671 The meta type is the same as the field-“name” but remove “test” E.g. “datetime”, “integer” type and so on.

All seem to validate in a predictable way, e.g. the email type must be a valid email in the textbox, except the “Url” meta type which doesn’t seem to validate at all(?).

The “file”-type is multi file upload initially.

“imagefile” type has a preview of the image.

“dictionary” doesnt seem to have any remove value function(?).

If invalid data is entered, a red * will appear next to the field and in the top of the page upon save.

A little warning though, this is tested in Chrome web browser which isn’t the best browser when using the Commerce Manager (IE 7 is recommended). Some types might behave behave in a better way in Internet Explorer.

Extra warning: when I added all the different meta fields the “Catalog Node Edit” function stopped working in Commerce Manager UI. Like this:

There is probably one of the properties that is not working correctly in the Commerce manager UI (buggy). And the function BindMetaForm() just fails.

Lesson learned: mess gently, very gently with commerce meta properties!

More on the subject – How to Create custom metafields controls in the UI: http://sdk.episerver.com/commerce/1.1.1/Content/Developers%20Guide/Architecture/ExtendCustomizeMetaFieldControls.htm