Grooper 21.00.0082 is available as of 12-12-2023! Check the  Downloads Discussion  for the release notes and to get the latest version.
Grooper 23.00.0042 is available as of 03-22-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0018 is available as of 04-15-2024! Check the  Downloads Discussion  for the release notes and to get the latest version.
Options

Visual Studio and Script Issues

[Deleted User][Deleted User] Posts: 0 admin
edited February 2018 in The Astronauts (Q&A)

Cannot Create a New Script

"VSTA template file is missing" When Creating a Script

This behavior is exhibited on both 2.6 > 2.7 upgrades and new databases/instances created in 2.7.  When attempting to create a script (via the Create button) on an appropriate Tree Node item, an error is displayed in the Output information.
ERROR: VSTA template file is missing: C:\Program Files\BIS\Grooper\GrooperScriptingTemplate.vstax

Compiling Existing Scripts in Administration

"Type 'Grooper.DataModel' is not defined' When Compiling Existing Script

When attempting to compile an existing script within Administration, the following errors are reported.
Error (BC30002) on line 18, column 35 of ScriptingSession.vb
  Type 'Grooper.DataModel' is not defined.
The compile process was stopped with 1 errors.

Cannot Edit Existing Scripts in Visual Studio

Visual Studio Community 2013 with VSTA Update 1 Fails to Launch

For scripts that were in place before upgrading from 2.6 to 2.7, clicking the Edit in Visual Studio button fails and reports an error in the Output information.
Error launching Visual Studio IDE: Operation is not valid due to the current state of the object.

Comments

  • Options
    [Deleted User][Deleted User] Posts: 0 admin
    edited March 2018
    The inability to create scripts (the first issue) is no longer present with the latest build (released on March 23, 2018).

    The other two issues are still present.  Is there any documentation that details script changes when upgrading from 2.7?
  • Options
    rmccutcheonrmccutcheon Posts: 756 ✭✭✭
    edited March 2018
    Here is what I was told about those, an article has not been wrote yet but it is on the to do list in Jira..

    Several namespaces have change from Grooper 2.60 to 2.70:  e.g. DataModel and BatchFolder have both moved from Grooper to Grooper.Core.  It is generally not considered best practice to use fully qualified class/type names (in the attached example, it should be "DataModel" instead of Grooper.DataModel).  Especially in this case since we are importing the referenced classes   Removing the "Grooper." from "DataModel" will resolve this situation.  

    Some exceptions regarding the above would be qualifying the name to avoid ambiguity (e.g. "Grooper.Core.DataTable" would be specific, but "DataTable" could be ambiguous with "System.Data.DataTable") or referencing a class once.
Sign In or Register to comment.