I suggest you...

Remove forced dependancy checks on Schema and Maps like ESB does

How many times do you have to remove a full Application or many applications just to update a schema or map?
The ESB toolkit largely removes this by using the strong name of assemblies in the rules / text.

29 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Stephen W Thomas shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Alastair Grant commented  ·   ·  Flag as inappropriate

        I think all errors about dependencies should be changed to a warning with the ability to override - especially when the strongname of the artefact being updated hasn't changed.

        i.e. if you're keeping the same assembly version and you have dependent resources then you should only receive a warning that you are changing something that may have an impact.

        It's common practice to use shared libraries but these are inherently used across the board and if you want to bug fix then you either need to remove all your applications from BizTalk or mess around with publisher policies - which in themselves seem to be asking for more trouble than just allowing overwriting of resource.

      Feedback and Knowledge Base