Podbrezova vs Spartak Trnava

Expert Analysis: Podbrezova vs Spartak Trnava

The upcoming match between Podbrezova and Spartak Trnava promises to be an exciting encounter, with several betting predictions indicating a dynamic game. The odds suggest a high probability of goals, with over 1.5 goals standing at 94.60% and over 2.5 goals at 65.30%. The average total goals are expected to be around 4.07, which aligns with these predictions. Both teams scoring is also likely, with a probability of 65.40%. The first half seems crucial, as the home team has a significant chance (70.30%) to score early on, while the away team is also poised to make an impact in both halves (68.50% in the first half and 59.30% in the second half). Additionally, the likelihood of both teams not scoring in either half is relatively balanced at 69.70% for the first half and 63.70% for the second half.

Regarding card predictions, under 5.5 cards are favored at 70.60%, suggesting disciplined play from both sides. However, there’s still a considerable chance for more bookings, with over 4.5 cards at 52.10%. Yellow cards are expected to average around 2.29 per match, while red cards are predicted to be slightly higher at an average of 1.28 per game.

Betting Predictions

• Home Team To Score In 1st Half: 70.30%
• Over 1.5 Goals: 94.60%
• Both Teams Not To Score In 1st Half: 69.70%
• Under 5.5 Cards: 70.60%
• Over 2.5 Goals: 65.30%
• First Goal Between Minute 0-29: 62.60%
• Away Team To Score In 1st Half: 68.50%
• Away Team To Score In 2nd Half: 59.30%
• Home Team To Score In 2nd Half:71GKX/Visual-Studio-2013-Customization/README.md
  # Visual Studio Customization

  This repository contains some useful customizations for Visual Studio.
  It’s based on [this blog post](http://www.bretth.dev/post/visual-studio-customization-part-3) by Bret Thalman.

  ## Install

  * Download and install [Visual Studio SDK](http://www.microsoft.com/en-us/download/details.aspx?id=40758).
  * Download this repository.
  * Open `Customizations.vsct` file in Visual Studio.
  * Build it.

  ## Customize

  You can customize `Customizations.vsct` file according to your needs.

  ## License

  MIT License.
  GKX/Visual-Studio-2013-Customization> # Visual Studio Customization Part III – Command Bars
  **By Bret Thalman**

  In this article we will cover how you can add command bars to your own custom tool windows or even existing ones.

  I’m going to assume that you’ve read my previous articles on Visual Studio customization because I’ll be building upon what we’ve done so far.

  Let’s start by looking at our VSCT file:

  
  

  
  

  
  

  
  

  
  

  
  

  ‘$(var.BretThalmanProjectRoot)resToolWindow.ico’
  PersistanceOnly

  
  
  

  
  

  …
  …
  …
  …
  …
  …
  …
  _1009 “My Custom Command Bar”
  _1010 “Add My Custom Command Bar”
  _1011 “Remove My Custom Command Bar”
  _1012 “Group Menu Item”
  _1013 “Group Menu Item Sub Menu”
  _1014 “Group Menu Item Sub Menu Item”

  
  _1024 “Running My Command…”
  _1025 “Completed My Command!”
  _1026 “Failed My Command!”

  
  _1034 “”

  
  _1040 “”
  _1041 “My Tool Window”

  …

  …

  …

  …

  …

  …

  …

  …

  ### Adding a new command bar

  To add a new command bar you must first create it as part of your tool window definition like I did above:

  
  
  

  As you can see here I gave my command bar the ID `commandBarID50000`. That means that I need to reference this ID somewhere else so that I can actually use this command bar.

  In order to do this I need to add another section called “ just below my “ section:

  …

  …
  …
  …

  Inside of this section I now need to add some XML code for my actual command bar:

  …

  
  

  <![CDATA[
  // If you want your toolbar always visible then just return S_OK;
  // Otherwise if you want it hidden until certain conditions are met
  // Then return S_FALSE; otherwise return E_FAIL;
  STDMETHODIMP CVisibilityConstraints::GetVisible()
  {
  // Get access to services used by other parts of VS
  CComPtr& spApp = m_pUnkSite->GetControllingUnknown();
  CComQIPtr& spDTE = spApp;

  if (spDTE != NULL)
  {
  BOOL bVisible = FALSE;

  // Check if DTE is visible
  if (spDTE->get_IsVisible() == VARIANT_TRUE)
  {
  // Check if any files are open
  CComPtr& spProjectItems = spDTE->get_ProjectItems();
  long lCount = spProjectItems->get_Count();

  if (lCount > -1)
  bVisible = TRUE;
  }

  return bVisible ? S_OK : S_FALSE;
  }

  return E_FAIL;
  }
  ]]>

  
  

  <![CDATA[

  <!DOCTYPE Commands [

  ]>

  ]]>

  The first part here defines whether or not this toolbar should ever show up and under what circumstances:

  …

  
  

  <![CDATA[
  // If you want your toolbar always visible then just return S_OK;
  // Otherwise if you want it hidden until certain conditions are met
  // Then return S_FALSE; otherwise return E_FAIL;
  STDMETHODIMP CVisibilityConstraints::GetVisible()
  {
  // Get access to services used by other parts of VS
  CComPtr& spApp = m_pUnkSite->GetControllingUnknown();
  CComQIPtr& spDTE = spApp;

  if (spDTE != NULL)
  {
  BOOL bVisible = FALSE;

  // Check if DTE is visible
  if (spDTE->get_IsVisible() == VARIANT_TRUE)
  {
  // Check if any files are open
  CComPtr& spProjectItems = spDTE->get_ProjectItems();
  long lCount = spProjectItems->get_Count();

  if (lCount > -1)
  bVisible = TRUE;
  }

  return bVisible ? S_OK : S_FALSE;
  }

  return E_FAIL;
  }
  ]]>

  …

  If you don’t care about any special conditions then just replace everything inside `CDATAP[]` with `return S_OK;`.

  The next part specifies what commands will be displayed on each toolbar:

  …

  
  

  <![CDATA[

  <!DOCTYPE Commands [

  ]]

  ]]>

  …

  This XML block allows us to specify multiple items including separators between them.

  The most important thing here though is that every item must have an `Id` attribute specified and that `Id` must match something from elsewhere in our VSCT file such as a button or menu item.

  So lets say that I wanted my custom tool window’s button (`cmdIdMyCommand`) along with two new menu items (`menuId30001` & `menuId30002`) placed onto my new custom tool window’s new custom command bar (`commandBarID50000`).

  Here’s how I would do that:

  

  And here’s how my XML looks like now:

  

  ### Adding menus within menus

  Adding nested menus within menus isn’t too difficult either but there are some gotchas involved so let me walk through them step-by-step for you!

  First off let me show you what my desired end result looks like:

  

  Now let’s look at how I achieved this result!

  #### Step One: Add Your Menus into Your Main Menu

  First off lets look at how my main menu looks right now:

  

  As you can see all three submenus don’t actually exist yet!

  So lets go ahead and add them into my main menu by adding some XML code right below where I defined my main menu:

  

  Now lets take a look again:

  

  As you can see they’re all defined but they’re not showing up!

  #### Step Two: Make Sure They’re Visible

  Now let me explain why they aren’t showing up yet!

  Remember earlier when I told you that every item had an `Id` attribute specified and that `Id` had to match something from elsewhere in our VSCT file?

  Well there was one more thing… That was **each submenu had its own unique GUID**!

  So basically instead of having something like `

  `, it needs something like ``.

  So let me go ahead and fix those two submenus by adding their respective GUIDs:

  

  Now lets take another look!

  

  Okay great! Now they’re showing up but they’re empty!

  #### Step Three: Add Items Into Your Submenus

  Okay now its time for us fill out those submenus!

  First off lets take a look at what those two submenus currently contain:

  

  As you can see they’re empty!

  So lets go ahead and add some items into them by adding some XML code right below where I defined them:

  

  And now take another look!

  

  Great! Now they have content but their contents aren’t showing up properly!

  #### Step Four: Make Sure Their Contents Are Visible

  Now remember earlier when I told you about how every item had an Id attribute specified?

  Well there was one more thing… That was **each submenu needed its own unique GUID** too!

  So basically instead of having something like “, it needs something like “.

  So let me go ahead and fix those two submenus by adding their respective GUIDs:

  

  And now take another look!

  

  Okay great! Now everything shows up correctly except for one little problem…

  #### Step Five: Fix The Last Missing Piece Of Our Puzzle

  Okay finally lets take care of the last piece missing from our puzzle… The last submenu within the last submenu which doesn’t exist yet!

  We’ll follow exactly the same steps as before except this time its going inside another submenu!

  First off let me show you how things currently look right now:

  

  As usual all three submenus don’t actually exist yet!

  So lets go ahead and add them into their parent submenu by adding some XML code right below where I defined their parent submenu:

  

  Now lets take a look again!

  

  As usual they’re all defined but they’re not showing up!

  Remember earlier when I told you about how every item had its own unique GUID?

  Well there was one more thing… That was **each submenu had its own unique GUID**!

  So basically instead of having something like `

  `, it needs something like ``.

  So let me go ahead and fix those two submenus by adding their respective GUIDs:

  

  And now take another look!

  

  Great! Now they’re showing up but they’re empty!

  Lets fill out those submenus next by adding some XML code right below where I defined them:

  

  And now take another look!

  

  Great! Now they have content but their contents aren’t showing up properly!

  Remember earlier when I told you about how every item had its own unique GUID?

  Well there was one more thing… That was **each submenu needed its own unique GUID** too!

  So basically instead of having something like “, it needs something like “.

  So let me go ahead and fix those two submenus by adding their respective GUIDs:

  

  And finally take another look!

  

  Okay great! Everything shows up correctly now except for one last little problem…

  #### Step Six: Fix The Last Missing Piece Of Our Puzzle

  Okay finally lets take care of the last piece missing from our puzzle… The last submenu within the last submenu which doesn’t exist yet!

  We’ll follow exactly the same steps as before except this time its going inside another submenu inside another submenu…

  First off let me show you how things currently look right now…

  

  As usual all three submenus don’t actually exist yet…

  So lets go ahead and add them into their parent submenu by adding some XML code right below where I defined their parent submenu…

  

  Now lets take a look again…

  

  As usual they’re all defined but they’re not showing up…

  Remember earlier when I told you about how every item had its own unique GUID?

  Well there was one more thing… That was **each submenu had its own unique GUID**!

  So basically instead of having something like `

  `, it needs something like ``.

  So let me go ahead and fix those two submenus by adding their respective GUIDs…

  

  And now take another look…

  ![image]() Image014.jpg )

  Great! Now they’re showing up but they’re empty!

  Lets fill out those submenus next by adding some XML code right below where I defined them…

  ![image]() Image015.jpg )

  And now take another look…

  ![image]() Image016.jpg )

  Great! Now they have content but their contents aren’t showing up properly…

  Remember earlier when I told you about how every item had its own unique GUID?

  Well there was one more thing… That was **each submenu needed its own unique GUID** too!

  So basically instead of having something like “, it needs something like “.

  So let me go ahead and fix those two submenus by adding their respective GUIDs:

  ![image]() Image017.jpg )

  And finally take another look…

  ![image]() Image018.jpg )

  Okay great! Everything shows up correctly now!

  ### Conclusion

  And thats pretty much all there is too know about creating menus within menus within menus within menus etc etc etc lol…

  Hopefully after reading through this article everything makes sense enough so that hopefully someone else wont have as hard time trying figure out whats going on behind-the-scenes 🙂

  Thanks for reading!

  <!–
  This file contains common definitions used across multiple VSCT files.
  To import definitions from this file use syntax similar to following example:

  <!–

  –>

  –>

  <!–
  The following attributes control general options associated with files containing elements described in MSDN documentation topic [Extending Visual Studio Tools Using Menus , Toolbars , Status Bars , Property Pages , Wizards , Macros , Snippets , Dialog Boxes , Color Pickers , Task Pads , Search Filters ]( http : / / msdn . microsoft . com / en – us / library / jj162124(v=vs .80).aspx ).
  These attributes may appear anywhere before any element declaration occurs.
  See [XML Namespaces Overview ]( http : / / msdn . microsoft . com / en – us / library / ff687295(v=vs .80).aspx )for details regarding namespaces .
  Attribute description follows.
  Note NamespaceURI Attribute Name Description Attribute Value Format Example Notes Visibility Constraint Defines whether UI element should be visible based upon condition provided in VisibilityConstraintAttribute Code segment VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode string string string Example: VisibilityConstraintAttribute Type=SccProvider Name=SccProvider IsTeamExplorerCompatible=false Note When Type=SccProvider Name=SccProvider IsTeamExplorerCompatible=false Code segment provides value returned from method QuerySccProvider(). If value returned equals zero UI element won’t be visible.If value returned equals non-zero UI element will be visible.Note Method QuerySccProvider() must reside inside class derived from IVSVisibilityConstraint interface.Note Method QuerySccProvider() must reside inside class derived from IVSVisibilityConstraint interface.Note When Type=SccProvider Name=SccProvider IsTeamExplorerCompatible=true Code segment provides value returned from method QuerySccProviders(). If value returned equals zero UI element won’t be visible.If value returned equals non-zero UI element will be visible.Note Method QuerySccProviders() must reside inside class derived from IVSVisibilityConstraint interface.Note Method QuerySccProviders() must reside inside class derived from IVSVisibilityConstraint interface.Visibility Constraint Defines whether UI element should be visible based upon condition provided in VisibilityConstraintAttribute Code segment VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode string string string Example: VisibilityConstraintAttribute Type=QueryVsCategory Name=QueryVsCategory IsTeamExplorerCompatible=false Note When Type=QueryVsCategory Name=QueryVsCategory IsTeamExplorerCompatible=false Code segment provides value returned from method QueryVsCategory(). If value returned equals zero UI element won’t be visible.If value returned equals non-zero UI element will be visible.Note Method QueryVsCategory() must reside inside class derived from IVSVisibilityConstraint interface.Visibility Constraint Defines whether UI element should be visible based upon condition provided in VisibilityConstraintAttribute Code segment VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode string string string Example: VisibilityConstraintAttribute Type=UserDefined Name=UserDefined IsTeamExplorerCompatible=false Note When Type=UserDefined Name=UserDefined IsTeamExplorerCompatible=false Code segment provides value returned from method UserDefined(). If value returned equals zero UI element won’t be visible.If value returned equals non-zero UI element will be visible.Note Method UserDefined() must reside inside class derived from IVSVisibilityConstraint interface.Visibility Constraint Defines whether UI element should be visible based upon condition provided in VisibilityConstraintAttribute Code segment VisibilityConstraintAttribute visibilityconstrainttype visibilityconstraintcode VisibilityConstraintAttribute visibilityconstrainttype visibilitycontrastype string string int Example: Note When Type=UserDefined Name=UserDefined IsTeamExplorerCompatible=true Code segment provides boolean flag indicating whether category “Name” exists.If category “Name” exists returns true.If category “Name” doesn’t exist returns false.Example: Note Method UserDefined() must reside outside class derived from IVSVisibiltyContraint interface.Visibility Constraint Defines whether UI element should be visible based upon condition provided in ConditionExpressionCode Segment ConditionExpressionCodeSegment language=csharp expression Exmaple language=csharp expression Example csharp bool bShowElement;IVsHierarchy pHierarchy;VSCOMPONENTITEMFLAGS dwCompItemFlags;pHierarchy=pSolution->GetActiveProject();bShowElement=(pHierarchy!=NULL);bShowElement=bShowElement&&(dwCompItemFlags&VSCOMPONENTITEMFLAGS_VCBUILDABLE)!=0;bShowElement=bShowElement&&(dwCompItemFlags&VSCOMPONENTITEMFLAGS_REFERENCE)==0;if(bShowElement)bRetVal=S_OK;else bRetVal=S_FALSE.Condition Expression Provides mechanism allowing developers check presence or absence specific component properties during initialization phase.During initialization phase properties listed below could potentially influence decision regarding displaying particular component.Element’s property availability depends upon current state application.Element’s property availability depends upon current state application.Name Associated with property being checked.Name Associated with property being checked.Type Associated with property being checked.Type Associated with property being checked.Value Returned From Property Evaluation.Value Returned From Property Evaluation.String String Int Int String String Int String String Int Example csharp bool bIsWebApplication,pHier;pHier=pSolution->GetActiveProject();bIsWebApplication=(pHier!=NULL)&&pHier->IsKindOf(SID_SWebContainer);Example csharp bool bHasProperty,pHier;pHier=pSolution->GetActiveProject();bHasProperty=(pHier!=NULL)&&pHier->GetProperty("bHasProperty",out varValue);Example csharp bool bIsWebApplication,pHier,pProj;pProj=pSolution->GetActiveProject();bIsWebApplication=(pProj!=NULL)&&(pProj->IsKindOf(SID_SWebContainer));Example csharp bool bHasProperty,pHier,pProj;pProj=pSolution->GetActiveProject();bHasProperty=(pProj!=NULL)&&(pProj->GetProperty("bHasProperty",out varValue));Note Language Used For Writing Condition Expression.Code Segment Must Contain Valid Expression For Specified Language.Code Segment Must Contain Valid Expression For Specified Language.Language Used For Writing Condition Expression.Code Segment Must Contain Valid Expression For Specified Language.Code Segment Must Contain Valid Expression For Specified Language.Language Used For Writing Condition Expression.Code Segment Must Contain Valid Expression For Specified Language.Code Segment Must Contain Valid Expression For Specified Language.Language Used For Writing Condition Expression.Code Segment Must Contain Valid Expression For Specified Language.Code Segment Must Contain Valid Expression For Specified Language.Language Used For Writing Condition Expression.Code Segment Must Contain Valid Expression For Specified Language.Code Segment Must Contain Valid Expression For Specified Language.Example VBScript Dim oHierarchy Dim oSolution Dim oPropDim sPropName Dim sPropValue Set oSolution =<% oService.GetGlobalService(GetType(EnvDTE.Solution)) %> if (not oSolution.IsNull()) then if (oSolution.ActiveConfiguration.ConfigurationManager.ActiveConfiguration.IsDebugConfiguration()) then sPropName="bIsDebugMode";else sPropName="bIsReleaseMode";end if</%> oHierarchy=oSolution.ActiveConfiguration.Project.SetProperty(sPropName,sPropValue);ConditionExpression Provides mechanism allowing developers check presence or absence specific component properties during initialization phase.During initialization phase properties listed below could potentially influence decision regarding displaying particular component.Element’s property availability depends upon current state application.Element’s property availability depends upon current state application.Name Associated With Property Being Checked.Name Associated With Property Being Checked.Type Associated With Property Being Checked.Type Associated With Property Being Checked.Value Returned From Property Evaluation.Value Returned From Property Evaluation.String String Int Int String String Int String String Int Example VBScript Dim oHierarchy Dim oSolution Dim oPropDim sPropName Dim sPropValue Set oSolution =<% oService.GetGlobalService(GetType(EnvDTE.Solution)) %> if (not oSolution.IsNull()) then if (oSolution.ActiveConfiguration.ConfigurationManager.ActiveConfiguration.IsDebugConfiguration()) then sPropName="bIsDebugMode";else sPropName="bIsReleaseMode";end if</%> oHierarchy=oSolution.ActiveConfiguration.Project.SetProperty(sPropName,sPropValue);Example VBScript Dim oHierarchy Dim oSolDim sConfigDim iConfigDim iCfgCntDim iCfgIdxDim sCfgNamDim Set oSol =<% oService.GetGlobalService(GetType(EnvDTE.Solution)) %> iCfgCnt=oSol.Count(iCfgCnt);for(iCfgIdx=iCfgIdx;iCfgIdx<iCfgCnt;iCfgIdx++)oSol.Item(iCfgIdx).Properties("cchConfigurations")="cchConfigurations";next;i=i>i?i:i+1;i=i==i?i+1:iExample VBScript Dim oHierarchy,oSol,oPrj,oPjT,cfg,i,cfgcnt,cfgidx,cfgnam,oPrjT,vrtp,vrtt,vrtpval Set oSol =<% oService.GetGlobalService(GetType(EnvDTE.Solution))  %> if(not(oSol.isNull()))then cfgcnt=oSol.Count(cfgcnt);for(cfgidx=cfgidx,cfgcnt,cfgidx++)cfignam=oSol.Item(cfgidx).Properties("cchConfigurations")cfg=oSol.Item(cfgidx).Properties("cchProjectsInConfiguration")vrtp="cchProjectsInConfiguration.vrtp",vrtpval vrtpt="cchProjectsInConfiguration.vrtpt",vrtt cfg(vrtp)=vrtpval cfg(vrtpt)=vrtt end if vrt=vrt&gt?vrt:vrt+11 vrt=vrt==vrt?vrt+11:vrtEnd IfConditionExpression Provides mechanism allowing developers check presence or absence specific component properties during initialization phase.During initialization phase properties listed below could potentially influence decision regarding displaying particular component.Element’s property availability depends upon current state application.Element’s property availability depends upon current state application.Name Associated With Property Being Checked.Name Associated With Property Being Checked.Type Associated With Property Being Checked.Type Associated With Property Being Checked.Value Returned From Property Evaluation.Value Returned From Property Evaluation.String String Int Int String String Int String String Int Example VBScript Dim bResult,bCanDebug,bCanDeploy,bCanTest,bCanProfile,bCanEdit,bCanView ProjectItem pPI Project pP Project pP Solution pSLn pSLn ActiveDocument ActiveDocument View View Set pSLn =<%oService.GetGlobalService(GetType(EnvDTE._Solution))% &gt ;Set pPI =<%oTargetObject % &gt ;If(pPI.Collection.Parent.Project.Kind <> VSPROJ_KIND_UNKNOWN)pP =<%pPI.Collection.Parent.Project % &gt ;If(pP.Kind <&gt VSPROJ_KIND_UNKNOWN)bResult=FalseEnd IfIf(pSLn.IsBuildPossible(bCanDebug,bCanDeploy,bCanTest,bCanProfile,bCanEdit,bCanView))ThenIf(bResult)(bResult=bResult OrElse(bCanDebug OrElse(bCanDeploy OrElse(bCanTest OrElse(bCanProfile)))) End IfEnd IfEnd IfIf(pP.CanStartDebugger)=TrueThenIf((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_VSTESTPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_VSOLEEXTENSIONPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_VSBUILDPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_MSILMERGEPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_MSILMERGEUIPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_MSILMERGEUIWIZARDPROJECT))) AndAlso((Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJ_TYPE_MSILMERGEUICONTROLPROJECT)))&&(Not(pPI.Collection.Parent.Project.IsKindOf(SOLEDITPROJTYPE.VSPROJTYPED_VSSOLUTIOOOOOOOOOOOOOOOOOOOON))))))))))))ThenbResult=TrueEnd IfEnd IfConditionExpression Provides mechanism allowing developers check presence or absence specific component properties during initialization phase.During initialization phase properties listed below could potentially influence decision regarding displaying particular component.Element’s property availability depends upon current state application.Element’s property availability depends upon current state application.Name Associated With Property Being Checked.Name Associated With Property Being Checked.Type Associated With Property Being Checked.Type Associated With Property Being Checked.Value Returned From Property Evaluation.Value Returned From Property Evaluation.String String Int Int String String Int String String Int Example VBScript Const vsBuildNone=-2147483647 Const vsBuildRunToCursor=-2147483646 Const vsBuildRunToCursorOnce=-2147483645 Const vsBuildRunUntilReturn=-2147483644 Const vsBuildGo=-2147483643 Const vsBuildGoToCursor=-2147483642 Const vsBuildGoToCursorOnce=-2147483641 Const vsBuildGoUntilReturn=-2147483640Const VsToolsOptionsContributionKey As Long VsToolsOptionsContributionKey=''''''''''''''"d7a442d6-bd48-438f-bc26-dab8e92741f9""</commandtable