BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
JayDZimmerman
Fluorite | Level 6

Using Chris Hemedinger's amazing book and downloadable examples/templates, we have begun developing custom tasks for EG (7.1).  We are about to go full bore into this, and were wondering if anyone had experience developing with a version of Visual Studio beyond 2013.  We would like to use Visual Studio 2017 since it is our current standard, but didn't know if we would encounter issues with the .NET Framework version, debugging interface, or using Chris' templates.  Anyone have ideas on this?

1 ACCEPTED SOLUTION

Accepted Solutions
ChrisBrooks
Ammonite | Level 13

I don't think you should encounter problems with the .NET Framework since you can specify which one to use inside Visual Studio (as long as you have the version you want to use installed). I would also have thought you would be OK with the templates but as Andrew saya Chris Hemedinger is the authority on this.

View solution in original post

5 REPLIES 5
ChrisBrooks
Ammonite | Level 13

I don't think you should encounter problems with the .NET Framework since you can specify which one to use inside Visual Studio (as long as you have the version you want to use installed). I would also have thought you would be OK with the templates but as Andrew saya Chris Hemedinger is the authority on this.

CaseySmith
SAS Employee

@ChrisBrooks is correct.  Using Visual Studio 2017 to create your custom tasks is completely fine *as long as* you target a version of the .NET Framework that is compatible with the version of EG or AMO you intend to run the tasks in.

 

The following table shows the .NET Framework version that was targeted by each EG (and AMO) version:

 

SAS Enterprise Guide .NET Framework
7.1, 7.11, 7.12, 7.13 4.5.1
6.1 4.0
5.1 4.0
4.3 3.5

 

For a custom task to be compatible with a specific EG/AMO version, it must target the same or earlier .NET Framework version. For example, if your custom task targeted .NET Framework 3.5, it should work in EG 4.3 and later.

 

This also means you can't accept the default .NET Framework version used in Visual Studio 2017, since it is 4.7, which is newer than the current latest version targeted by EG/AMO; you'll have to change it to target an older .NET Framework version, depending on which versions of EG/AMO you wish to support.

 

Casey


Register today and join us virtually on June 16!
sasglobalforum.com | #SASGF

View now: on-demand content for SAS users

JayDZimmerman
Fluorite | Level 6

Thank you all for the great input.  It sounds like we should be able to move forward with VS 2017 as long as we set the correct framework target (that chart is really helpful).  I'll try copying the template files to the 2017 directory and hope that Microsoft hasn't changed the format since 2013; it wouldn't be the first time they've done that to me.

AndrewHowell
Moderator

@JayDZimmerman - don't forget to vote for your preferred accepted solution (if applicable).

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 5 replies
  • 1381 views
  • 4 likes
  • 4 in conversation