Workflow Soluiton

 View Only
  • 1.  "Select data Type" takes a minute to open.

    Posted Oct 21, 2014 08:44 AM

    I have a workflow with an integration towards vmware sdk when I select data types ( for Input data, Output data, For each loops, return type for script component and all other locations where a Type selection is needed) it takes from 50 sec to 2 minutes before the "Select Data Type" dialog is displayed.
    I have a huge list of types and without counting I would guess that there is about 3000 types in Win25Service2010 alone. 
    It takes this long each time I open the dialog and no difference if I open it before so my conclusion is that there is no caching on the types.
    I would like to know if there is a workaround to speed this up.

     



  • 2.  RE: "Select data Type" takes a minute to open.

    Posted Oct 21, 2014 08:50 AM

    I thought these types were cached as well.. one thing you can try to do to speed it up is getting rid of any other project references that aren't needed (such as ASDK, ASDKTask and Resource, which are added by default)



  • 3.  RE: "Select data Type" takes a minute to open.

    Posted Oct 21, 2014 09:10 AM

    Hi

    I have removed all unneeded project references, but as vmware sdk contains over 3000 types getting rid of a few types from other project references did not change the situation noticeable. 

     

    //Mickael



  • 4.  RE: "Select data Type" takes a minute to open.

    Posted Oct 21, 2014 09:30 AM

    You have a couple of options, but it involves a bit of work.

    The first solution is to handcode the comps using only the types needed (this may not be an option if you don't have access to an IDE or are unfamiliar with the component API or C#). When you handcode, you have control of what to include/exclude unlike the generators.

    The second solution depends on what type of generator you used. If you're using a web service generator, I suggest breaking out the web services you hit across multiple integration projects (assuming there are multiple web services). That way, you include only the types needed with each model/project. I forget if the web service generator has an option of excluding types like the Resource generator does, but that's an option as well if it can be done.