How can I launch ILDASM from the VS.NET 2003 IDE?
Launch VS.NET and choose Tools->External Tools->Add and add settings as show below: Title: ILDASM (or anything else of your choice) Command: C:\Program Files\Microsoft.NET\SDK\v1.1\Bin\ildasm.exe Arguments: $(TargetPath) Initial Directory: $(TargetDir) Use Output Window: unchecked Prompt for arguments: unchecked Close on exit: checked.
How can I populate a TreeView Control with XML Data?
The following articles on MSDN give you step by step instructions on how you can populate a TreeView Control with data from an XML file. C#: Populate a TreeView Control with XML Data in Visual C# .NET VB.NET: Populate a TreeView Control with XML Data in Visual Basic .NET
How can I open a project created with Visual Studio .NET 2003 in Visual Studio .NET 2002?
Check out the following article in CodeProject : A Utility to Convert VS.NET 2003 Project Files.
How do I determine which button in a Toolbar is clicked?
When you click on a button on a Toolbar the click is sent to the Toolbar, so you need to check the ToolBarButtonClickEventArgs’s button property to determine the button on the Toolbar that was clicked. [C#] private void toolBar1_ButtonClick(object sender, System.Windows.Forms.ToolBarButtonClickEventArgs e) { //check if toolBarButton1 was clicked if (e.Button == toolBarButton1) { MessageBox.Show(‘Button 1 clicked’); } } [VB.NET] Private Sub toolBar1_ButtonClick(ByVal sender As Object, ByVal e As System.Windows.Forms.ToolBarButtonClickEventArgs) ’check if toolBarButton1 was clicked If e.Button = toolBarButton1 Then MessageBox.Show(‘Button 1 clicked’) End If End Sub
What are the common issues in redirecting assemblies using the publisher policy files?
1) Make sure to follow proper naming conventions for the policy dll. For example, if the original assembly name is TestAssembly.dll then the corresponding policy assembly should be called ‘policy.1.0.TestAssembly.dll’ to make this redirection work for all ‘1.0.*’ version bindings of the original assembly. 2) While specifying the name for the assembly in the policy file, do not include the ‘.dll’ extension. This is wrong: >assemblyIdentity name=’TestAssembly.dll’ publicKeyToken=’f638d0a8d5996dd4′ culture=’neutral’ /< Instead use: >assemblyIdentity name=’TestAssembly’ publicKeyToken=’f638d0a8d5996dd4′ culture=’neutral’ /< 3) Make sure to sign the policy assembly with the same strong name as the original. 4) Make sure to distribute the policy file along with the policy assembly. Installing the policy assembly in the GAC alone will not suffice. Note that any change made to the policy file after creating the policy assembly will not take effect. 5) Always use /link (to the policy file) in the ‘al’ command while creating the policy assembly. Do not use /embed. It doesn’t seem to be supported. Some good links: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconcreatingpublisherpolicyfile.asp http://www.newtelligence.com/downloads/downloads-basta2001.aspx http://www.only4gurus.com/DotNet/studies/managevers.htm