Using Visual SourceSafe in Microsoft Visual Studio: "Using Visual SourceSafe in Microsoft Visual Studio
Visual SourceSafe is used within Visual Studio in the form of two plug-ins that are compatible with the Visual Studio IDE. These SourceSafe plug-ins run in the source control portion of the IDE, using the source control adapter package of Visual Studio. For more about Visual Studio source control, see 'Source Control in Visual Studio' in the Visual Studio Help."
Monday, December 7, 2009
» Using SourceSafe in Visual Studio 2005 & 2008
» Using SourceSafe in Visual Studio 2005 & 2008: "Using SourceSafe in Visual Studio 2005 & 2008"
Microsoft SourceSafe and Visual Studio source control integration articles
Microsoft SourceSafe and Visual Studio source control integration articles: "Microsoft Visual SourceSafe and Visual Studio source control integration help and tips
Disclaimer: The purpose of these pages is to answer some of the questions that appeared most frequently on SourceSafe newsgroups.
Their content is provided to you 'AS IS', and does not confere any rights.
Microsoft Visual SourceSafe and Source Control resources
Installing and configuring Microsoft Visual SourceSafe for Internet (Remote) access
About Visual SourceSafe Passwords and Security
Source Control Bindings explained
Microsoft Source Control Interface"
Disclaimer: The purpose of these pages is to answer some of the questions that appeared most frequently on SourceSafe newsgroups.
Their content is provided to you 'AS IS', and does not confere any rights.
Microsoft Visual SourceSafe and Source Control resources
Installing and configuring Microsoft Visual SourceSafe for Internet (Remote) access
About Visual SourceSafe Passwords and Security
Source Control Bindings explained
Microsoft Source Control Interface"
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview: "MagicDisc is freeware. It is very helpful utility designed for creating and managing virtual CD drives and CD/DVD discs. For anyone who deals with CD-based programs – it is a MUST. MagicDisc allows you to use almost all CD/DVD image without burning them onto CD or DVD in order to easily access your favorite games, music, or software programs ---- It works like a real CD/DVD-ROM: You can run programs, play games, or listen to music from your virtual CD-ROM. Allowing you to run your game images at over 200x faster than from a conventional CD/DVD-ROM."
Download details: Microsoft Visual Studio 2010 Ultimate Beta 2
Download details: Microsoft Visual Studio 2010 Ultimate Beta 2: "Microsoft Visual Studio 2010 Ultimate Beta 2 - ISO
Brief Description
Microsoft Visual Studio 2010 Ultimate simplifies solution development, lowering risk and increasing return. Tools for every stage of the lifecycle, from design and development through test and deployment, let you unleash your imagination and deliver impactful solutions. This download is an ISO image that can be burned to blank media for installation."
Brief Description
Microsoft Visual Studio 2010 Ultimate simplifies solution development, lowering risk and increasing return. Tools for every stage of the lifecycle, from design and development through test and deployment, let you unleash your imagination and deliver impactful solutions. This download is an ISO image that can be burned to blank media for installation."
Friday, December 4, 2009
Working with SharePoint lists, Part 2 - Windows SharePoint Services - Microsoft Office Online
Working with SharePoint lists, Part 2 - Windows SharePoint Services - Microsoft Office Online: "Microsoft Windows® SharePoint® Services technology
This tutorial teaches you how to view information in lists based on Microsoft Windows SharePoint Services. It is the second of a two-part tutorial. In the first part, Working with SharePoint lists, Part 1, you learned the basic steps of creating a list, adding columns, and adding new list items. You should complete Part 1 before you take this tutorial.
In this tutorial, you will continue to use the example of your team's visit to Trey Research to learn how to sort and filter list items so you can find and manage information more easily. You also learn how to create a view so that you can specify more advanced display settings and save them."
This tutorial teaches you how to view information in lists based on Microsoft Windows SharePoint Services. It is the second of a two-part tutorial. In the first part, Working with SharePoint lists, Part 1, you learned the basic steps of creating a list, adding columns, and adding new list items. You should complete Part 1 before you take this tutorial.
In this tutorial, you will continue to use the example of your team's visit to Trey Research to learn how to sort and filter list items so you can find and manage information more easily. You also learn how to create a view so that you can specify more advanced display settings and save them."
Introducing the List Item Filter web part - Weblog Ton Stegeman [MVP]
Introducing the List Item Filter web part - Weblog Ton Stegeman [MVP]: "Introducing the List Item Filter web part
After having introduced the Content By Type web part, I got questions on how to filter the content of this web part. After writing a number of articles on filter web parts, I decided it was time to add a custom filter web part to the content by type package. The first filter web part in that package is the List Item Filter web part. A bit like the out of the SharePoint List Filter, but without the popup for users to select filter values. The List Item Filter has 4 options. It can render as:
* Dropwdown list
* Radio button list
* Checkbox list
* Tag cloud ( I used the code from the Community Kit for SharePoint Tag Cloud webpart)
If you think ‘that is nice, but filter web parts are only available if I have the Enterprise license.’ at this point, keep on reading! This filter web part will also work in MOSS Standard and even in WSS!"
After having introduced the Content By Type web part, I got questions on how to filter the content of this web part. After writing a number of articles on filter web parts, I decided it was time to add a custom filter web part to the content by type package. The first filter web part in that package is the List Item Filter web part. A bit like the out of the SharePoint List Filter, but without the popup for users to select filter values. The List Item Filter has 4 options. It can render as:
* Dropwdown list
* Radio button list
* Checkbox list
* Tag cloud ( I used the code from the Community Kit for SharePoint Tag Cloud webpart)
If you think ‘that is nice, but filter web parts are only available if I have the Enterprise license.’ at this point, keep on reading! This filter web part will also work in MOSS Standard and even in WSS!"
How to use a SharePoint ItemAdded event handler and the object model to submit data from an InfoPath form to a SharePoint list
How to use a SharePoint ItemAdded event handler and the object model to submit data from an InfoPath form to a SharePoint list: "This article explains how you can use an ItemAdded event handler on a Form Library to extract data from an InfoPath form that was submitted to the form library and use this data to add a new item to a custom SharePoint list.
Problem
You want to save the data that is entered into an InfoPath form to a SharePoint list, but InfoPath does not allow you to submit data to a SharePoint list.
Solution
You could use one of the following 5 methods:
1. Use the SharePoint Lists web service together with a CAML batch update to add an item to a SharePoint list.
2. Use a SharePoint Designer workflow to get data from the InfoPath form and create a SharePoint list item.
3. When using an InfoPath browser form, call directly into the SharePoint object model from within the InfoPath form to add an item to the SharePoint list.
4. Use a SharePoint event handler feature to make calls directly into the SharePoint object model to add an item to the SharePoint list when an InfoPath form is added to a Form Library on which the event handler has been activated.
5. Use a custom Visual Studio workflow to add an item to the SharePoint list when an InfoPath form is added to a Form Library on which the workflow has been set to run.
This article discusses method 4."
Problem
You want to save the data that is entered into an InfoPath form to a SharePoint list, but InfoPath does not allow you to submit data to a SharePoint list.
Solution
You could use one of the following 5 methods:
1. Use the SharePoint Lists web service together with a CAML batch update to add an item to a SharePoint list.
2. Use a SharePoint Designer workflow to get data from the InfoPath form and create a SharePoint list item.
3. When using an InfoPath browser form, call directly into the SharePoint object model from within the InfoPath form to add an item to the SharePoint list.
4. Use a SharePoint event handler feature to make calls directly into the SharePoint object model to add an item to the SharePoint list when an InfoPath form is added to a Form Library on which the event handler has been activated.
5. Use a custom Visual Studio workflow to add an item to the SharePoint list when an InfoPath form is added to a Form Library on which the workflow has been set to run.
This article discusses method 4."
Writing Event Handlers and Attaching/Detaching using Features « Rehman Gul [MVP, MCTS SharePoint]
Writing Event Handlers and Attaching/Detaching using Features « Rehman Gul [MVP, MCTS SharePoint]: "In this post, I am going to write an event handler that:
1. is triggered when an item is added to a document library (i.e. ItemAdded)
2. sends an email to some email address notifying that an item has been added to the document library
3. is deployed to a List using SharePoint Features
Okey, lets get started. Create a subsite under your site collection. In the subsite create a Document Library named AlertMe.
JumpStart – > JumpStartWeb -> AlertMe"
1. is triggered when an item is added to a document library (i.e. ItemAdded)
2. sends an email to some email address notifying that an item has been added to the document library
3. is deployed to a List using SharePoint Features
Okey, lets get started. Create a subsite under your site collection. In the subsite create a Document Library named AlertMe.
JumpStart – > JumpStartWeb -> AlertMe"
How to: Create an Event Handler Feature
How to: Create an Event Handler Feature: "How to: Create an Event Handler Feature
This example shows how to add a simple event handler that prevents items from being deleted from a list. Two procedures are involved in this task:
*
Creating an event handler in Microsoft Visual Studio
*
Adding the event handler as a Feature in Windows SharePoint Services"
This example shows how to add a simple event handler that prevents items from being deleted from a list. Two procedures are involved in this task:
*
Creating an event handler in Microsoft Visual Studio
*
Adding the event handler as a Feature in Windows SharePoint Services"
Registering an Event Handler
Registering an Event Handler: "Registering an Event Handler
Event handlers are registered differently in Windows SharePoint Services 3.0 because of new concepts like content types and Features that it introduces. For backward compatibility reasons, however, Windows SharePoint Services 3.0 supports the existing registration of library events. The EventSinkAssembly, EventSinkClass, and the EventSinkData properties continue to function and are exposed in the user interface."
Event handlers are registered differently in Windows SharePoint Services 3.0 because of new concepts like content types and Features that it introduces. For backward compatibility reasons, however, Windows SharePoint Services 3.0 supports the existing registration of library events. The EventSinkAssembly, EventSinkClass, and the EventSinkData properties continue to function and are exposed in the user interface."
Event Receiver Definition: Data and Filter
Steven Van de Craen's Blog [MVP]: "Event Receiver Definition: Data and Filter
I recently declared an Event Receiver through a SharePoint Feature: Event Registrations
Some of the samples online had surprising elements such as <Data /> and <Filter />. I have never seen them used before and didn’t know their purpose. Perhaps they are not to be messed with ? Perhaps great power lies within ?
* Data – Specifies a string that will be passed as a parameter to the receiver method when handling the event
This one is commonly found in the documentation. It can be used to declare additional information and then the Event Receiver code behind can use this information. Better than hardcoding although I haven’t had the need for it (yet ?).
* Filter – Reserved. Filter MUST be NULL
According to the official docs it is reserved: Event Receivers Result Set"
I recently declared an Event Receiver through a SharePoint Feature: Event Registrations
Some of the samples online had surprising elements such as <Data /> and <Filter />. I have never seen them used before and didn’t know their purpose. Perhaps they are not to be messed with ? Perhaps great power lies within ?
* Data – Specifies a string that will be passed as a parameter to the receiver method when handling the event
This one is commonly found in the documentation. It can be used to declare additional information and then the Event Receiver code behind can use this information. Better than hardcoding although I haven’t had the need for it (yet ?).
* Filter – Reserved. Filter MUST be NULL
According to the official docs it is reserved: Event Receivers Result Set"
How to read web.config settings in itemAdded event handler?
How to read web.config settings in itemAdded event handler?: "When you register your even receiver from code
See the Using object model to attach Event Receiver to List section on Event Receivers chapter on SharePointDevWiki
http://www.sharepointdevwiki.com/display/public/Event+Receivers
or declaratively
EventReceiver Element (DeploymentManifest)
http://msdn.microsoft.com/en-us/library/bb250202.aspx
then you can set the data property (limited to 255 charcters)
SPEventReceiverDefinition.Data Property
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventpropertiesbase.receiverdata.aspx
You can get this late using the SPEventPropertiesBase.ReceiverData property in your receiver:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventpropertiesbase.receiverdata.aspx
This property is also available in SPItemEventProperties (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spitemeventproperties.aspx) that is a sublcass of SPEventPropertiesBase.
For example:
public override void ItemAdding(SPItemEventProperties properties)
{
string configValue = properties.ReceiverData;
}
But I thing the length maximum for this property is rather limiting."
See the Using object model to attach Event Receiver to List section on Event Receivers chapter on SharePointDevWiki
http://www.sharepointdevwiki.com/display/public/Event+Receivers
or declaratively
EventReceiver Element (DeploymentManifest)
http://msdn.microsoft.com/en-us/library/bb250202.aspx
then you can set the data property (limited to 255 charcters)
SPEventReceiverDefinition.Data Property
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventpropertiesbase.receiverdata.aspx
You can get this late using the SPEventPropertiesBase.ReceiverData property in your receiver:
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.speventpropertiesbase.receiverdata.aspx
This property is also available in SPItemEventProperties (http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spitemeventproperties.aspx) that is a sublcass of SPEventPropertiesBase.
For example:
public override void ItemAdding(SPItemEventProperties properties)
{
string configValue = properties.ReceiverData;
}
But I thing the length maximum for this property is rather limiting."
How to read web.config settings in itemAdded event handler?
How to read web.config settings in itemAdded event handler?: "For example, if you add System.configuration.dll assembly to you references, and add this using directive:
using System.Configuration;
then in an ItemAdding method you can get the value 'UserName' from appSettings like this:
string userName = ConfigurationManager.AppSettings['UserName'];"
using System.Configuration;
then in an ItemAdding method you can get the value 'UserName' from appSettings like this:
string userName = ConfigurationManager.AppSettings['UserName'];"
SPEventPropertiesBase.ReceiverData Property (Microsoft.SharePoint)
SPEventPropertiesBase.ReceiverData Property (Microsoft.SharePoint): "SPEventPropertiesBase.ReceiverData Property (Microsoft.SharePoint)
Gets a string that contains data about the event."
Gets a string that contains data about the event."
EventReceiver Element (DeploymentManifest)
EventReceiver Element (DeploymentManifest): "EventReceiver Element (DeploymentManifest)"
EventReceiver Element (DeploymentManifest)
EventReceiver Element (DeploymentManifest): "EventReceiver Element (DeploymentManifest)
Represents a SharePoint event receiver object instance (SPEventReceiverDefinition). Depending on the event receiver collection specified, the event receiver can listen for events on SPFile, SPList, SPListItem, or SPWeb objects."
Represents a SharePoint event receiver object instance (SPEventReceiverDefinition). Depending on the event receiver collection specified, the event receiver can listen for events on SPFile, SPList, SPListItem, or SPWeb objects."
EventReceiver Element (DeploymentManifest)
EventReceiver Element (DeploymentManifest): "EventReceiver Element (DeploymentManifest)"
EventReceiver Element (DeploymentManifest)
EventReceiver Element (DeploymentManifest): "EventReceiver Element (DeploymentManifest)
Represents a SharePoint event receiver object instance (SPEventReceiverDefinition). Depending on the event receiver collection specified, the event receiver can listen for events on SPFile, SPList, SPListItem, or SPWeb objects."
Represents a SharePoint event receiver object instance (SPEventReceiverDefinition). Depending on the event receiver collection specified, the event receiver can listen for events on SPFile, SPList, SPListItem, or SPWeb objects."
Event Receiver Definition: Data and Filter
Steven Van de Craen's Blog [MVP]: "Event Receiver Definition: Data and Filter
I recently declared an Event Receiver through a SharePoint Feature: Event Registrations
Some of the samples online had surprising elements such as <Data /> and <Filter />. I have never seen them used before and didn’t know their purpose. Perhaps they are not to be messed with ? Perhaps great power lies within ?
* Data – Specifies a string that will be passed as a parameter to the receiver method when handling the event
This one is commonly found in the documentation. It can be used to declare additional information and then the Event Receiver code behind can use this information. Better than hardcoding although I haven’t had the need for it (yet ?).
* Filter – Reserved. Filter MUST be NULL"
I recently declared an Event Receiver through a SharePoint Feature: Event Registrations
Some of the samples online had surprising elements such as <Data /> and <Filter />. I have never seen them used before and didn’t know their purpose. Perhaps they are not to be messed with ? Perhaps great power lies within ?
* Data – Specifies a string that will be passed as a parameter to the receiver method when handling the event
This one is commonly found in the documentation. It can be used to declare additional information and then the Event Receiver code behind can use this information. Better than hardcoding although I haven’t had the need for it (yet ?).
* Filter – Reserved. Filter MUST be NULL"
Thursday, December 3, 2009
Custom Web Part to Display file (.html, .txt, .xml) contents
The following code builds a web part, that can disply the contents on any file(.txt, .xml, .html are tested so far) on the page.
After adding the web part to the page, edit the web part properties and in the miscellanious section specifiy the file location (e.g. C:\Foler\FileName.txt).
using System;
using System.IO;
using System.Runtime.InteropServices;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
namespace CLIENTName.WebPartName
{
[Guid("1cba1a69-02b8-482c-b634-73cad1a46aa6")]
public class WebPartName: System.Web.UI.WebControls.WebParts.WebPart
{
string filePath = @"C:\MyHTML.htm";
[WebBrowsable(true), WebDisplayName("File Path"), WebDescription("Enter the file path"), Personalizable(PersonalizationScope.Shared)]
public String FilePath { get { return filePath; } set { filePath = value; } }
public WebPartName ()
{
}
protected override void CreateChildControls()
{
base.CreateChildControls();
Label label = new Label();
//label.Text = "Hello World";
label.Text = GetFileContents(this.FilePath);
this.Controls.Add(label);
}
/// <summary>
///
/// </summary>
/// <param name="FullPath"></param>
/// <returns></returns>
public string GetFileContents(string FullPath)
{
string strContents = null;
StreamReader objReader = default(StreamReader);
try
{
objReader = new StreamReader(FullPath);
strContents = objReader.ReadToEnd();
objReader.Close();
return strContents;
}
catch (Exception Ex)
{
throw Ex;
}
}
}
}
Wednesday, December 2, 2009
XML CDATA
XML CDATA: "All text in an XML document will be parsed by the parser.
But text inside a CDATA section will be ignored by the parser.
PCDATA - Parsed Character Data
XML parsers normally parse all the text in an XML document.
When an XML element is parsed, the text between the XML tags is also parsed:
<message>This text is also parsed</message>
The parser does this because XML elements can contain other elements, as in this example, where the <name> element contains two other elements (first and last):
<name><first>Bill</first><last>Gates</last></name>
and the parser will break it up into sub-elements like this:
<name>
<first>Bill</first>
<last>Gates</last>
</name>
Parsed Character Data (PCDATA) is a term used about text data that will be parsed by the XML parser.
CDATA - (Unparsed) Character Data
The term CDATA is used about text data that should not be parsed by the XML parser.
Characters like '<' and '&' are illegal in XML elements.
'<' will generate an error because the parser interprets it as the start of a new element.
'&' will generate an error because the parser interprets it as the start of an character entity.
Some text, like JavaScript code, contains a lot of '<' or '&' characters. To avoid errors script code can be defined as CDATA.
Everything inside a CDATA section is ignored by the parser.
A CDATA section starts with '<![CDATA[' and ends with ']]>':
<script>
<![CDATA[
function matchwo(a,b)
{
if (a < b && a < 0) then
{
return 1;
}
else
{
return 0;
}
}
]]>
</script>
In the example above, everything inside the CDATA section is ignored by the parser.
Notes on CDATA sections:
A CDATA section cannot contain the string ']]>'. Nested CDATA sections are not allowed.
The ']]>' that marks the end of the CDATA section cannot contain spaces or line breaks."
But text inside a CDATA section will be ignored by the parser.
PCDATA - Parsed Character Data
XML parsers normally parse all the text in an XML document.
When an XML element is parsed, the text between the XML tags is also parsed:
<message>This text is also parsed</message>
The parser does this because XML elements can contain other elements, as in this example, where the <name> element contains two other elements (first and last):
<name><first>Bill</first><last>Gates</last></name>
and the parser will break it up into sub-elements like this:
<name>
<first>Bill</first>
<last>Gates</last>
</name>
Parsed Character Data (PCDATA) is a term used about text data that will be parsed by the XML parser.
CDATA - (Unparsed) Character Data
The term CDATA is used about text data that should not be parsed by the XML parser.
Characters like '<' and '&' are illegal in XML elements.
'<' will generate an error because the parser interprets it as the start of a new element.
'&' will generate an error because the parser interprets it as the start of an character entity.
Some text, like JavaScript code, contains a lot of '<' or '&' characters. To avoid errors script code can be defined as CDATA.
Everything inside a CDATA section is ignored by the parser.
A CDATA section starts with '<![CDATA[' and ends with ']]>':
<script>
<![CDATA[
function matchwo(a,b)
{
if (a < b && a < 0) then
{
return 1;
}
else
{
return 0;
}
}
]]>
</script>
In the example above, everything inside the CDATA section is ignored by the parser.
Notes on CDATA sections:
A CDATA section cannot contain the string ']]>'. Nested CDATA sections are not allowed.
The ']]>' that marks the end of the CDATA section cannot contain spaces or line breaks."
Tuesday, December 1, 2009
Department Of Aerospace Engineeering -Research
Department Of Aerospace Engineeering -Research: "Computational Fluid Dynamics: Aerospace applications, Algorithms: kinetic schemes, Unstructured meshes, meshless solvers, DNS/LES. Unsteady flow computations using chimera cloud of points. Cardiovascular fluid dynamics."
Symptoms / Treatments
Symptoms / Treatments: "Symptoms / Treatments
For Indigestion Treatment:
* Don't eat quickly, take your time, eat slowly and enjoy
* Drink fluids after rather than during meals
* Try to relax after eating
* Do not exercise after eating. Rather, exercise before a meal or at least one hour after eating
* Wait at least three hours after your last meal of the day before going to bed
* Avoid midnight snacking
* Minimize Stress
* And if you do get indigestion, try Alka-Seltzer Original for fast relief of acid indigestion with headache or body aches. Alka-Seltzer is also available in Lemon-Lime flavor.
For Heartburn Treatment:
* To remedy heartburn, avoid overeating. Don't eat large meals, instead try smaller, more frequent meals.
* Avoid dishes that are:
o Acidic, like tomatoes, citrus fruits, garlic and onions
o High in fat and oils (animal and vegetable)
o Contain caffeine, like chocolate and coffee
o Very spicy - like curry and cayenne pepper
* To remedy heartburn:
o Don't lie down right after eating. If you have to, keep your head elevated (at least 6 inches) above your feet and lie on your left side
o Avoid tight-fitting garments
o Cut down on alcohol consumption
* And if you do get heartburn, use Alka-Seltzer Heartburn Relief, specially formulated as a heartburn treatment to extinguish the fire of heartburn fast."
For Indigestion Treatment:
* Don't eat quickly, take your time, eat slowly and enjoy
* Drink fluids after rather than during meals
* Try to relax after eating
* Do not exercise after eating. Rather, exercise before a meal or at least one hour after eating
* Wait at least three hours after your last meal of the day before going to bed
* Avoid midnight snacking
* Minimize Stress
* And if you do get indigestion, try Alka-Seltzer Original for fast relief of acid indigestion with headache or body aches. Alka-Seltzer is also available in Lemon-Lime flavor.
For Heartburn Treatment:
* To remedy heartburn, avoid overeating. Don't eat large meals, instead try smaller, more frequent meals.
* Avoid dishes that are:
o Acidic, like tomatoes, citrus fruits, garlic and onions
o High in fat and oils (animal and vegetable)
o Contain caffeine, like chocolate and coffee
o Very spicy - like curry and cayenne pepper
* To remedy heartburn:
o Don't lie down right after eating. If you have to, keep your head elevated (at least 6 inches) above your feet and lie on your left side
o Avoid tight-fitting garments
o Cut down on alcohol consumption
* And if you do get heartburn, use Alka-Seltzer Heartburn Relief, specially formulated as a heartburn treatment to extinguish the fire of heartburn fast."
Customizing the Quick Launch menu: Adding fly-out menus to SharePoint navigation
Microsoft SharePoint Team Blog : Customizing the Quick Launch menu: Adding fly-out menus to SharePoint navigation: "Customizing the Quick Launch menu: Adding fly-out menus to SharePoint navigation"
Coalesys, DHTML client controls, ASP, JSP, ASP.NET server controls, navigation and layout
Coalesys, DHTML client controls, ASP, JSP, ASP.NET server controls, navigation and layout: "The original DHTML hierarchical menu system, offering consistent, flexible, cross-platform support. Whether you program in ASP.NET, ASP (32- or 64-bit), JSP or using any other web development tool, WebMenu is for you! Available separately, or as part of the Mercury-UI products. New Version 5.0 contains a number of significant, as well as minor, enhancements."
One of the (DARDEM) client is using this for there sharepoint site. paid some what $300 for n number of users.
One of the (DARDEM) client is using this for there sharepoint site. paid some what $300 for n number of users.
Subscribe to:
Posts (Atom)
Posts
