NEWSLETTER
 Note: SlidingMenu v2.0 is NOT compatible with vs2005, please do not try to install SlidingMenu v2.0 with your vs2005 - it will not work.
With layered areas you can hold a lot more information on a lot less space - SlidingMenu slide through these layers!
  Menulab home >> SlidingMenu >> How to Upgrade         ASP.NET Offsite Freelance Programmer  
 
SlidingMenu version 2.0 is very superior to GroupedCollection 1.0 - see History, also code examples added to this website will be written for SlidingMenu. If you have installed GroupedCollection version 1.0, I recommend you take the trouble to upgrade.
Unfortunately you need to adress several issues if upgrading:
1. GroupedCollection must be deinstalled, go to "Start | Settings | Control Panel | Add/Remove Programs | GroupedCollection" and choose Remove.
2. The GroupedCollection should be removed from your Toolbox (not necessary but nice)
3. IntelliSense XSD background should be removed for GroupedCollection (not necessary but nice)
4. XML file integrating with VS.NET IDE Dynamic Help should be removed (not necessary but nice)
5. SlidingMenu must be installed, see How to Install.
6. If you want to use SlidingMenu in a project where GroupedCollection is already used, you must:
a. delete the Webmodelling.GroupedCollection assembly from your projects bin-folder (the SlidingMenu assembly cannot reside in the same bin directory as the GroupedCollection assembly)
b. remove the reference to Webmodelling.GroupedCollection in Solution Explorer under your Project | References
c. change the @Register declaration on top of pages already using the GroupedCollection to point at the Webmodelling.SlidingMenu assembly
d. change all occurences of <wm:GroupedCollection ... to <wm:SlidingMenu ...
e. change all occurences of <GroupedCollectionStyle ... to <SlidingMenuStyle ...
f. eventually namespaces regarding the GroupedCollection in the BODY tag of Web Forms should be removed (not necessary but nice)
g. SlidingMenu self repair namespaces, therefore even if you have not dragged SlidingMenu from the Toolbox, SlidingMenu will try to set in correct namespace then you switch to design-view. The correct (case sensitive) namespace to set in the BODY tag is:
xmlns:wm="http://www.menulab.com/schemas/SlidingMenu-v2-0-IntelliSense"
h. the GroupedCollection installer installed an Add-in to your VS.NET IDE, this Add-in is no longer necessary, you should remove it (not necessary but nice). Click on "Tools | Add-in Manager" and deselect the GCNamespace.
i. depending on your ASP.NET editor, you can use the compiler to clean up your code-behind code. (GroupedCollection to SlidingMenu, GroupCollectionStyle to SlidingMenuStyle, GroupDataBoundEventHandler to SlidingMenuGroupEventHandler and GroupDataBoundEventArgs to SlidingMenuGroupEventArgs)
note:
If you have a paid license of GroupedCollection version 1.0, you can get the same license of SlidingMenu version 2.0 for free, just mail me your license number and I mail you a new license number back to use with the SlidingMenu version 2.0 (GroupedCollection Standard License corresponds to SlidingMenu Professional License).
note:
If you have trouble upgrading, contact me at rasmus@menulab.com (also for freeware users).
Contact Menulab   |   Terms & Conditions   |   Privacy Policy   |   Sitemap   |   Copyright © Menulab 2003. All rights reserved.