Posts Tagged ‘Tools’

Quite a long time that Message Box Viewer in fully integrated with BizTalk360, which is awesome, because MBV is, or was, the perfect tool to analyze and identifying potential issues in the BizTalk environment.

MBV had over 400 rules that were able to verify different configurations/settings on your BizTalk Server environment, gathering the results in order to provide information about the general health of the environment to the administrations teams, like:

  • Whether backup jobs, or any BizTalk Job, are configured and running properly
  • Whether default throttling settings are changed or custom adapters are added to your environment
  • Whether the BizTalk databases are at their optimum levels in terms of size
  • Performance issues
  • And so on…

BizTalk 360 took advantage of the power of MBV and integrated it, in past versions of the product, n its architecture to the present day. By integrating MBV, BizTalk360 was capable to offer the following additional values to the users:

  • The ability to perform scheduled execution of MBV
  • Show reports categorized in a nicer way
  • Have a single platform to monitor and analyze BizTalk Server environments

BizTalk360 V8.0 has the same capabilities, however, Message Box Viewer (aka MBV) is currently deprecated, and it was replaced by BizTalk Health Monitor (aka BHM) and it is no longer available for download. Of course if you are using BizTalk Server 2013 or higher you may know that MBV was included in BizTalk Server 2013 and you will find it in your BizTalk installation directory:

  • Normally at “C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Utilities\Support Tools\MsgBoxViewer”
  • Or “…\Microsoft BizTalk Server 2013 R2\SDK\Utilities\Support Tools\MsgBoxViewer” folder

I know that BizTalk360 team is already plan and working to fix it and integrate BizTalk Health Monitor (aka BHM) with BizTalk360 tool replacing the currently MBV.

However, BHM is based on the same engine as MBV, what happen was that the MBV project team, after releasing MBV as a standalone tool for several years, decided to integrate it more closely with the BizTalk Administration Console providing this way a quick and complete dashboard of a BizTalk group that will help BizTalk administrators to monitor the health of their BizTalk platform more effectively.

Previous MBV had an execution file call “MBVConsole.exe” (Console MBV Client tool) that allowed users to automatically schedule (via PowerShell or windows scheduler Task) and generate reports, same tool that BizTalk360 uses.

BHM no longer has this console tool (“MBVConsole.exe”). The tool was renamed to “BHMCollect.exe” but it is “exactly the same” as “MBVConsole.exe” in MBV… so I decided to give it a shot and see if I was able to use the last version of the tool inside BizTalk360.

I when to “Config and Schedule Message Box Viewer Integration” page inside BizTalk360:

  • Click the “Settings” icon at the top of the page and then selecting “Message Box Viewer” option from the left menu bar.

On “Config and Schedule Message Box Viewer Integration” panel, instead of configure the path to the MBV directory in the “Message Box Viewer Download Directory” property, I set the path to the Health Monitor BizTalk, in my case:

  • C:\Program Files (x86)\BizTalk Support Tools\BHMv3.1

MessageBox-Viewer-BizTalk360-integration-configurations

Of course this just is not enough, because as I told before, BizTalk360 is trying to use “MBVConsole.exe”. So, as a workaround, if you want to use the BHM integrated with BizTalk360 you need to:

  • Go to the BHM installation directory;
  • Make a copy of “BHMCollect.exe” and rename it to “MBVConsole.exe”
    • Important: do not rename the original file! You still need it as it is!
    • You will then have to files: “BHMCollect.exe” and “MBVConsole.exe” witch is exactly the same file!

BHM-integrated-BizTalk360-installation-folder

Now if you try to run it manually inside BizTalk360, you will see that it was able to execute and provide the reports in the same nice and beautiful way than using MBV.

BizTalk-Health-Monitor-BizTalk360-integration

Again, this solution is a workaround that you can use for now, because, BizTalk360 team is already plan and working to fix it and integrate BizTalk Health Monitor (aka BHM), replacing the currently MBV, in next versions of the product.

This is not really a critical problem because BHM is practically equal to MBV, but BHM may have some new improvements/hotfixes that you can use that MBV doesn’t have it.

I just released yesterday, but I’ve decided to do a small update to this tool bringing new functionalities in order to solve some limitations, especially Character Encoding problem.

Portuguese language have many letters with accents and while importing/reading the files in the previous version, all accented letters are printed as a question mark. It was obvious that I had a problem with Encoding.

Again, “Microsoft Message Queuing Testing Tool” is a simple tool that you can use to test sending files to Microsoft Queue in order to evaluate whether other applications are reading correctly the messages.

I’m using it to send messages to a queue that is being consumed by BizTalk Server

RELEASE NOTES

Version 2.0 brings:

  • Improvements in the “Message Label” auto fill
  • Improvements in the “Import Message File” functionality with better control of the encoder associated with the file
    • Add the ability to choose the code page identifier

Microsoft-Message-Queuing-Testing-Tool-v2

Hope you enjoy it.

You can download this tool here:

Microsoft Message Queuing Testing Tool (79,9 KB)
Microsoft | Code Gallery

In the last couple of days I been working (migrating a BizTalk Solution from BizTalk Server 2004 to BizTalk Server 2013 R2) in a solution that works deeply with Microsoft Message Queuing (MSMQ). It receives messages from private queue with the use of the MSMQ Adapter and send messages to other Queues (among other channels) that are consumed by other applications/servers.

And one of the things that I intended to do was partial tests, in a very simple way, to validate if all my receive ports were well configured in order to consume the expected messages.

Microsoft Message Queuing Testing Tool” is a simple tool that you can use to test sending files to Microsoft Queue.

Microsoft Message Queuing or MSMQ is a message queue implementation developed by Microsoft and deployed in its Windows Server operating systems and enables applications running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. It provides guaranteed message delivery, efficient routing, security, and priority-based messaging.

With this tool you can easily send messages to a queue in order to evaluate whether other applications are reading correctly the messages.

Microsoft-Message-Queuing-Testing-Tool

This tool allows you to set:

  • The queue where you want to send the files/messages
  • A Label associated to the file/message
  • The Queue transaction type
  • Import an existing file or manually add a message

Microsoft-Message-Queuing-Testing-Tool-result

And it will provide:

  • success of delivery information (with transaction id)
  • or error detail information

I like simple tool that allow me to test my integration scenarios/projects, so I decided today to take some of my time to create this very simple and basic tools, but at least for me, that will be very useful.

Hope you enjoy also.

You can download this tool here:

Microsoft Message Queuing Testing Tool (79,9 KB)
Microsoft | Code Gallery

It was with great pleasure that I presented, last Monday – August 31, 2015 – my second presentation in the Integration Monday series. This time I was invited to talk about my personal experience about BizTalk NoS Ultimate and how this tool can improve our efficiency, productivity and experience while developing BizTalk projects.

And for this session I decided to take the risk of not creating a storyboard, as I normally do, preparing all the details about the entire session, test all the demos, train the session over and over to try to reach the perfection and so on… instead I decided to just spend some time on creating 5 or 6 slides that could visually express the way I see and feel this tool. And choose 2 or 3 real projects in which I could emulate the tool as I usually do in my daily work life.

The intention was only to prepare the support base for the entire presentation and then try to explain the impact of using BizTalk NoS Ultimate in the Developer Lifestyle, the advantages and how it allows me to improve my productivity/efficiency in my BizTalk projects… as if someone walked right now into my office and I had to explain him why to use and why I love it!

(That’s why some times you will see some pauses during the presentation and some “ahhh”’s and maybe some things note working so well – the risks inherent in doing this type of approach – hehhehe)

Sandro-Pereira-Real-Case-Scenarios-Where-BizTalk-NoS-Ultimate-Can-Improve-Our-Efficiency-video

I hope you enjoyed and found this session informative and valuable, as I enjoyed doing it. And if you miss it or want to do see it again (I think anyone in their right mind wants to review) there are some good news… the video and slides from the session are now available in the Integration User Group site here:

I apologize for my voice, I was sick all week and my voice is a little husky (hoarse) – I don’t know very well the term in English – and despite being completely weird making a presentation to your computer, without seeing the people and their reactions – I’ve done four online sessions and it is impossible to get used to this format, I think I feel more comfortable being in front of an audience than making an online session hehehe – It was a pleasure to present once again in the Integration User Group.

Thank you for inviting me and see you all in a next time!

See also this amazing review made by Nino Crudele: BizTalk NOS Ultimate – BizTalk Assessment Power Up!

I’m glad to be back, once again, to Integration Monday Events! The first time I presented a session about “BizTalk Server Tips & Tricks for Developers and Admins (Deep Dive)” (June 22, 2015), a similar session that I also presented in BizTalk Summit 215 London, that you can found and watch online here.

This time I will present a session about BizTalk NoS Ultimate and how this tool can improve our efficiency, productivity and experience while developing BizTalk projects.

Real-Case-Scenarios-Where-BizTalk-NoS-Ultimate-Can-Improve-Our-Efficiency

Session Name: Real Case Scenarios Where BizTalk NoS Ultimate Can Improve Our Efficiency

Session Overview: In this session, I will show, using real cases scenarios, how can BizTalk NoS Ultimate will help BizTalk developers to improve their efficiency, productivity and experience while developing BizTalk projects. BizTalk NoS Ultimate is a time-saving tool and, as we pass through its functionalities, we show where developers can save valuable time while working on their day-to-day tasks.

Note that I’m not a seller, and I will not try to sell this tool, instead, I will only focus in share my experience in real case scenarios where this tool can help us, at least it helped me, while developing BizTalk Projects. The rest It’s up to you if you want to use it or not.

I invite you all to join us next Monday. Grab your “seat” by registering in this session here.

Exciting news for the BizTalk Community… specially the 200 persons that attended the BizTalk Summit 2014 London that already know the potential of BizTalk NoS addin!

Nino Crudele just public announce in is blog: BizTalk NoS Add-in Beta version has been officially released through Visual Studio Gallery that the BizTalk NoS Addin is now available for you to download it in install it on Visual Studio gallery at: BizTalk NoS Addin!!!!!

What is BTSG NoS Addin purpose?

The purpose of BTSG NoS addin is to help all BizTalk Developer, why not, all BizTalk Administrator too in a lot of different situations, by improving the developer experience and why not reduce the development time in new or existent BizTalk projects.

It will provide several functionalities like quick search inside artifact, fast register/unregister in GAC, find critical, internal or external dependencies… and many fore functionalities like JackHammering, which will compare your VS artifact with the artifact deployed in BizTalk environment, you can also extract the artifact (Orchestration, map, schema and so on) from BizTalk environment and put it in the VS solution or even test your pipeline in VS simply… several features that are usefully in our day by day work and a time saver in a lot of situations.

How can I install BTSG NoS Addin

You can install BTSG NoS Addin directly from Visual Studio “Extensions and Updates” option. For that you must:

  • Open Visual Studio as Administrator, go to the “Tools” menu and select the “Extensions and Updates” option.
  • In the “Extensions and Updates”, in the right panel select “Online” tab and search for “BizTalk” or for “BizTalk NoS Addin”.
  • And Download the BizTalk Nos Addin”.

The rest of the installation process is described in one of my previous post: How to install BTSG NoS Addin for Visual Studio 2012

You can find all the documentation about this addin in:

Or in my posts:

Special Note

It has been a challenge, an extreme playfulness and a privilege to work with my dear friend Nino Crudele! I feel extremely honored that Nino have chosen me to help in this final phase of his work and for that THANKS Nino!

_DSC2735

Now is time to take a small vacations of BizTalk NoS addin and finish my ongoing work: BizTalk Mapper Pattern eBook… witch of course Nino will be one of the reviewers J

In my last posts I’m being describing some of the features of BTSG NoS Addin. This is the final post about the overview of all features available with this Visual Studio addin and how can you use them.

Test Pipeline

There are many ways to test BizTalk pipelines: by using Biztalk Pipeline Framework to create unit testing, using the Pipeline.exe tool or by create and use them by implementing "for real" in BizTalk messaging scenarios. But there isn’t for real an easy build support feature in Visual Studio to test our custom pipelines.

Once again BizTalk NoS addin will provide that for you. This operation will test our custom pipeline pipelines directly from Visual STudio by simple right click and “Test Pipeline”:

BTSG-NoS-Addin-Test-Pipeline

  • Visual Studio will prompt a window for to select and instance of the message that you want to try against the pipeline.

BTSG-NoS-Addin-Test-Pipeline-open-file

  • and will show the result for the pipeline directly in VS IE

BTSG-NoS-Addin-Test-Pipeline-result

Test Pipeline Component

As the previous one testing or debugging a custom pipeline component can be a challenger and most of the times you will need to create and testing them by implementing and configuring a BizTalk messaging scenarios and then attach the BizTalk process in Visual Studio to debug the components.

You now will be able to debug your pipeline component attaching an external process from VS without care about BizTalk environment by:

  • Right click on the pipeline that contains the custom pipeline component that you want to try and select the option “Test Pipeline Component”:

BTSG-NoS-Addin-Test-Pipeline-Component

  • A window will be show that will describe all the steeps necessary for you to configure you testing scenario and debug the custom pipeline component

BTSG-NoS-Addin-Test-Pipeline-Component-2

  • The first thing you need to do is select an instance of a message that you want to try against the custom pipeline component, by clicking in the add wheel in the left:

BTSG-NoS-Addin-Test-Pipeline-Component-3

    • A window will prompt for to select and instance of the message

BTSG-NoS-Addin-Test-Pipeline-Component-open-file

  • The second step is to set a breakpoint in you custom pipeline component and attach the BTSG TestPipeline process with the Visual Studio Debugger by:
    • On the Visual Studio “Debug” menu, select “Attach to Process”

BTSG-NoS-Addin-Test-Pipeline-Component-attach-process

    • Select the BTSG.TestPipeline.exe process (the title will also contains the name of our pipeline) and click “Attach”

BTSG-NoS-Addin-Test-Pipeline-Component-attach-process-select

  • For the third and final step, you will need to go to the BTSG window to configure you testing scenario and debug the custom pipeline component, to submit the select message instance to debug it against the custom pipeline component, by clicking in the submit wheel in the right side:

BTSG-NoS-Addin-Test-Pipeline-Component-4

And you be able to start debug your custom pipeline component code.

Heuristics

Heuristics are basically the same of the above dependencies features (internal and external) but more useful during refactoring or before to do an update in an artifact. For example you need to modify an artifact and you want to know what will be the artifact update impact in the entire solution.

Other extreme situation could be, I want to know where this property schema or schema could be used, and this is not so simple to know because a property schema or schema could be used in lot of different way using his root nodes.

Heuristic Internal Propagation

This feature is basically the same as the “Internal Dependencies” but with the difference that we will also go ahead and will also the sub-levels of dependencies, i.e., the sub-artifacts.

BTSG-NoS-Addin-Heuristic-Internal-Propagation

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic Internal Propagation” option

BTSG-NoS-Addin-Heuristic-Internal-Propagation-option

Heuristic External Propagation

This feature is basically the same as the “External Dependencies” but with the difference that we will also go ahead and will also the sub-levels of dependencies, i.e., the sub-artifacts.

BTSG-NoS-Addin-Heuristic-External-Propagation

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic External Propagation” option

BTSG-NoS-Addin-Heuristic-External-Propagation-option

Heuristic Circular Propagation

This feature is basically the combination of both above heuristic operation (internal and external propagation) in a single operation.

BTSG-NoS-Addin-Heuristic-Circular-Propagation

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic Circular Propagation” option

BTSG-NoS-Addin-Heuristic-Circular-Propagation-option

Heuristic Anchoring Dependencies

Looking in all files in the solution for all artifact that could be associated with the artifact selected.

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic Anchoring Dependencies” option

BTSG-NoS-Addin-Heuristic-Anchoring-Dependencies-option

Heuristic Similarity Dependencies

Looking in all files in the solution for all artifact that could be associated (same solution domain, for example are using the same namespace) in any possible option, with the artifact selected.

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic Similarity Dependencies” option

BTSG-NoS-Addin-Heuristic-Similarity-Dependencies-option

Heuristic Contagion Dependencies

Looking in all files in the solution for all artifact that could be associated with the artifact selected, in all of possible combinations, type name, fields used, root name and more…

You can access this features by:

  • Right click in your resource (file) name and select the “Heuristic Contagion Dependencies” option

BTSG-NoS-Addin-Heuristic-Contagion-Dependencies-option

Finally all the features are documented… And we only need to wait the release announcement!!!!

In my last posts I’m being describing some of the features of BTSG NoS Addin. In this post we will continue to have an overview of all features available with this Visual Studio addin and how can you use them.

Locate it

How many times you open your old or new project will several files opened in the Visual Studio MDI window and you want a simple way to locate where this file is in your projects structure? For example: you are working in a transformation but know you need to locate the map file to specify a “TestMap Input Instance”… if don’t know exactly where it is, you need to check the full path of the map and then manually navigate in the solution explorer to the file that you want.

BTSG-NoS-Addin-Where-is-my-file

Finally now you will have an easy way to accomplish this! Which will save us much time in the developing process, for me this one of the basic stuff that is a timesaver.

Note: Even if you don’t have the “Solution Explorer” Window opened, this feature will find the file that you are locking for and will automatically open (or give the proper focus) the “Solution Explorer” window!

You can access these features by:

  • On the Visual Studio MDI window, right click in tab with the name of the file and select “Locate it!” option

BTSG-NoS-Addin-Locate-it

The result is, as you can see the picture below, the project will be expanded and the desired file will be selected:

BTSG-NoS-Addin-Locate-it-result

Again this is very useful for a BizTalk Developer because he needs to locate the file to test or generate schema instances or test, validate or debug maps.

Dependencies

This addin will provide several option to deal with dependencies between BizTalk artifacts. Choosing what to use will depend on the situation and what you want to archive.

External Dependencies

Sometimes we want to know who use this artifact. This is really useful in order to get a clear sense of where the changes that we need to do can have impacts. For example, if I need to change a schema, will this changes will have impact in my maps or in my orchestration? So I really need to know, before modifying my resource, which artifacts are using it.

You can access this features by:

  • Right click in your resource (file) name and select the “External Dependencies” option

BTSG-NoS-Addin-External-dependencies

The result is, as you can see the picture below, the project will be expanded and all the resources that are consuming the artifact will be selected:

BTSG-NoS-Addin-External-dependencies-result

Note: You will also have available the option to automatically open all the files (this is a behavior/functionality that you will find in many features).

BTSG-NoS-Addin-open-artifact-to-option

Internal Dependencies

Well if you like the previous one, this will be the opposite and also useful in several situations. In this case we want to know what this artifact is using (or which artifacts are consuming). For example: I need to modify the schema, or the schemas, used by a map… and you need to remember in huge solution this simple task to find schemas in your solution can be a challenger and a boring repeated task by BizTalk developers!

Don´t get me wrong, we have all the information on the map file by simply place the cursor over the schema:

BTSG-NoS-Addin-Where-is-my-file-schema

But again, out-of-the-box I don’t have any easy way to locate and open the schemas, I need to manually navigate in the solution explorer to the file that we want.

You can accomplish this by access this feature by:

  • Right click in your resource (file) name and select the “Internal Dependencies” option

BTSG-NoS-Addin-Internal-dependencies

The result is, as you can see the picture below, the project will be expanded and all the resources that being consumed by the artifact will be selected:

BTSG-NoS-Addin-Internal-dependencies-result

These are simple things/operations but they are timesaver for a BizTalk Developer. For example, about orchestration, I can ask internal dependencies and select the option “Open it”, because I want with one click to have available and ready to work all the artifact (schemas, maps and so on) to make all the necessary changes.

Critical dependencies

This feature van be found in the project context and will find all critical dependencies to solve the classical problem that you may have when deploying a project or solution, for example, an pipeline (or other artifact like map and so on) that exist in this project is being used by an external application, normally Visual Studio will generate an error about a foreign key database strict without to specify who the application is or what port that is using it.

BTSG-NoS-Addin-Visual-Studio-error-critical-dependencies

You can accomplish this by access this feature by:

  • Right click in the name of your project and select the “Critical Dependencies” option

BTSG-NoS-Addin-Critical-Dependencies

The result is, as you can see the picture below, the project will be expanded and all the resources that being consumed by the artifact will be selected:

BTSG-NoS-Addin-Critical-Dependencies-result

In this manner you can fix it and decide you deploy strategies

Heuristic Dependencies

We will talk about this features (there are 6 Heuristic Dependencies!) in another post.

Refactory

Similar with Reflector feature, the Refactory will create a more simple report with a circular reference (internal and external) with other artifacts that can be very useful to understand the refactory strategy to use.

You can accomplish this by access this feature by:

  • Right click on your artifact (Orchestration, map, schema…) and select the “Refactory” option

BTSG-NoS-Addin-Refactory

This feature will provide some statistics and information’s about

  • Who is using this artifact
  • And what artifacts this resource is consuming.
  • And some general information like complexity, persistent point and error handling (in orchestrations) and so on.

BTSG-NoS-Addin-Refactory-result

For several reasons some people don’t like the day of their birthday… I on the other hand love it! I enjoy celebrating the day with family and friends, receive gifts … but also give back something!

And as happens every year on this day, I always try to write a post for the BizTalk community… this year I will introduce the most expected features of BTSG NoS Addin… the infamous JackHammering!

BTSG-NoS-Addin-JackHammering

JackHammering

You can accomplish this by access this feature by:

  • Right click on your artifact (Orchestration, map, schema…) and select the “Jackhammering” option

BTSG-NoS-Addin-JackHammering-option

This features is useful for several things and will be mainly used to validate if the version we are using in development is or is not equal to the solution that is published in your BizTalk Server environment: DEV, E2E or even Production!

With this feature you can, for example:

  • Compare your artifact with artifact deployed in BizTalk Server environment or extract the artifact from BizTalk Server environment into your BizTalk Solution by:
    • Double click in your artifact (in this case the Orchestration) (Note: Nino is fixing the layout of the screen)

BTSG-NoS-Addin-JackHammering-orchestration

    • And an additional window will be presented for you to select the task you want to perform:

BTSG-NoS-Addin-JackHammering-menu

      • Compare it

BTSG-NoS-Addin-jackhammering-Compare-it

      • Or “Extract it” (in the left is the orchestration extract from BizTalk Server Environment and in the right is my orchestration version in Visual Studio)

BTSG-NoS-Addin-JackHammering-extract-it

  • Or you can accomplished the same task from an assembly file. This option is extremely useful if you import the DLL from production to compare to your version in developer, because normally the DEV machine cannot connect to production.

BTSG-NoS-Addin-JackHammering-from-assembly-file

  • When you choose “Extract form DLL” option, it will open a file explorer windows to select the DLL, the end result will be the same.

JackHammering will be useful for Developers but also for Admins. Developers can use it to for recover the solution to your BizTalk Developer machine because you lose your artifact (orchestration, map, schema and so on) code, or a normally situation when you arrive to the client and they don’t have the source code!! Or just because you aren’t sure if you are using the last version and so on.

But admin will also have a good way to validate if the solutions that are running are the right versions, if there is differences and knowing were problems can happen.

BTSG NoS Addin will be available soon… you just need to be a little more patience… stay tuned to Nino personal blog!

Last post I explain the propose of BTSG NoS Addin and start to descrive some of this features. In this post we will continue to have an overview of all features available with this Visual Studio addin and how can you use them.

Build Project

You are probably thinking you do I need another Build option? And the reason is simple, sometimes we have huge solution with several project inside, and in this situations try to build one simple project can be a challenger with Visual Studio because it simple takes a huge of time trying to make this task because all of dependencies.

This option will build the desired project without any interaction with Visual Studio design environment, making this operation faster than the native build operation on Visual Studio.

BTSG-NoS-Addin-Build-Project

You can access this features by:

  • Right click in your project name and select the “Build project” option

BTSG-NoS-Addin-Build-Project-option

Fast register/unregister in GAC quickly

How many times you desired to have a simple easy and quick way to install DLL, and why not also uninstall, in the Global Assembly Cache (GAC) and why not directly from your favorite developer tool: Visual Studio? Instead we need to install using Gacutil.exe tool, and don’t get me wrong, it is an excellent tool, but is not practical in the day by day work!

Finally now you have this option! At the moment is not a “direct” operation that you can do in your project. In other words you need additional but simple steps to accomplish these operations.

You can access these features by:

  • Select your project name and then in the solution explorer window click “Show All Files” option

BTSG-NoS-Addin-Show-All-Files

  • Navigate to the folder that contains the project DLL or the DLL that you want to register/unregister
    • For example: “\bin\debug”
  • Right click in the DLL name and select “Register in GAC” or “Unregister from GAC” options

BTSG-NoS-Addin-Register-Unregister-GAC-Visual-Studio

Note: This work with all DLL’s it doesn’t have to be a BizTalk DLL, you can easily register a C# Helper Class used by BizTalk Project in GAC with this functionality.

BTSG-NoS-Addin-Register-in-GAC

I personally LOVE this feature!

Deploy assembly

Again you are probably thinking you do I need another Deploy option? And the reasons are exactly the same as de “Build project” option that we described earlier.

This operation will deploy a BizTalk assembly directly from the bin directory in VS environment by simple right click and deploy it:

  • Select your project name and then in the solution explorer window click “Show All Files” option
  • Navigate to the folder that contains the project DLL that you want to deploy
    • For example: “\bin\debug”
  • Right click in the DLL name and select “Deploy assembly” option

BTSG-NoS-Addin-Deploy-2

This operation will be exactly the same as add/update resource from BizTalk Server administration console.
What’s the purpose? In some situations I simply don’t want to use Visual Studio environment will all the dependencies and other stuff. What I want is only to deploy the assembly fast.

This option will allow you to make this directly from Visual Studio, making this operation faster than the native deploy operation on Visual Studio.

BTSG-NoS-Addin-Deploy

BTSG NoS Addin will be available soon… you just need to be a little more patience… stay tuned to Nino personal blog!