Forum Discussion

DT's avatar
DT
Occasional Contributor
11 years ago

How to tackle Application Assembly Name changes

Our marketing team has decided to change the name of a product that is 3 years old and part of that change had the development team changing the application assembly names causing the name mapping to be invalid.  Is there a quick way to adjust for this in the name mapping without having to remap the entire application?



Old assembly name example: NameMapping.Sys.OurProduct.frmLogin...

New Assembly name example: NameMapping.Sys.OurProduct_Improved.frmLogin...



I dont foresee a problem updating over 300 scripts due too how we have them structured but remapping the application would take a decent amount of time as we are 5 weeks from release.
  • gid_216's avatar
    gid_216
    Frequent Contributor
    11 years ago


    Hi Dustin,



    Change the properties of the mapping object in nameMapping with out changing the Mapped Name. For this, you can use regular expressions if required.



    For Example: 



    For NameMapping.Sys.OurProduct_Improved.frmLogin,  you can use 

    NameMapping.Sys.OurProduct.frmLogin in your script(which is already been used), but in the "Mapped Objects" section of name mapping, the property for OurProduct will change if the new process name is Ourproduct_Improved, you can change with this else you can use OurProduct*.



    Hope this will help