Author Topic: Custom .Net Assembly References  (Read 3835 times)

mambo

  • New Community Member
  • Posts: 1
  • Hero Points: 0
Custom .Net Assembly References
« on: November 06, 2006, 08:14:28 pm »
In SlickEdit 11, I can create and compile using standard .Net framework assemblies.

But I have custom-build assemblies and cannot do the same.  Bombs off on my using statements.

In Visual Studio I'd add my assemblies as a Reference and all is well.

Please, what's the equivalent in SlickEdit 11?

TIA,

D

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5800
  • Hero Points: 461
Re: Custom .Net Assembly References
« Reply #1 on: November 08, 2006, 08:12:11 pm »
This should work.  Try adding a "C" language tag file (Tools>Tag Files...>click on "Add Tag File...".  Pick the "C" language, then you will get another dialog to specify a file name for the tag file.  After creating the tag file, then add the assembly to it by selecting your new tag file and clicking on "Add Files...".  This is where you select your assembly file.  When the assembly is updated, you'll need to use the "Rebuild Tag File..." button.

This isn't as good as the assembly being pickup from the source.  In order for SlickEdit to implement this, this would probably require a tag file cache mechanism which automatically creates/updates a tag file for each assembly when the #using is seen.  The "cached" tag file could be temporarily pulled in as an Extension Specific tag file. This could be written entirely as a macro.  I'm not sure what the best way to handle the "as_friend" option is.

Hope this help.

Dennis

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 3290
  • Hero Points: 463
Re: Custom .Net Assembly References
« Reply #2 on: November 08, 2006, 09:38:04 pm »
A quick clarification with respect to Clark's suggestions on how to set up tagging with .Net assemblies.  Unless you are actually writing managed C++, when you create the extension specific tag file, you probably want to create it for the languague you are using the assemblies in (C# or VB, for example).

From your original post, however, I get the impression that you are having trouble with building, not tagging, because it isn't finding the assemblies, is this correct? 

What kind of a project are you using?  A Visual Studio workspace, or a SlickEdit .NET SDK project, or your own custom thing?  If it is the latter, you can add the search paths to the build command by fine tuning what you find on Project > Project Properties, "Tools" tab, select "Build".