forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

VS2017 Plugin Causes Crash?

 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support
View previous topic :: View next topic  
Author Message
j clark



Joined: 29 Mar 2008
Posts: 20
Location: Bala Cynwyd (Pennsylvania)

PostPosted: Sun Jan 19, 2020 8:27 pm    Post subject: VS2017 Plugin Causes Crash? Reply with quote

I am using FTN95 with Visual Studio 2017. After a recent update to VS2017, when I try to add a .dll reference to a FTN95 project, VS2017 crashes with a message indicating the FTN95 1.0 plugin is the cause. Has anyone else experienced this?
Back to top
View user's profile Send private message
Robert



Joined: 29 Nov 2006
Posts: 330
Location: Manchester

PostPosted: Mon Jan 20, 2020 10:01 am    Post subject: Reply with quote

What version of Visual Studio do you have?
Back to top
View user's profile Send private message Visit poster's website
j clark



Joined: 29 Mar 2008
Posts: 20
Location: Bala Cynwyd (Pennsylvania)

PostPosted: Mon Jan 20, 2020 1:42 pm    Post subject: Reply with quote

Good afternoon Robert,

I am using VS2017 Version 15.9.19; .NET Version 4.8.03761; FTN95 Version 8.50, of course.
Back to top
View user's profile Send private message
Robert



Joined: 29 Nov 2006
Posts: 330
Location: Manchester

PostPosted: Mon Jan 20, 2020 6:38 pm    Post subject: Reply with quote

Is it a .NET project and what sort of DLL?
Back to top
View user's profile Send private message Visit poster's website
j clark



Joined: 29 Mar 2008
Posts: 20
Location: Bala Cynwyd (Pennsylvania)

PostPosted: Mon Jan 20, 2020 7:48 pm    Post subject: Reply with quote

The .dll's and the calling routines are .NET. The .dll's are written in both FTN95 and C#. They are different classes in different folders. They are older, working programs. The routine that tries to call them is itself a FTN95 Application Extension that is called by a C# main program. The applications are both Console apps (for debugging) and Windows Services (for release). The problem occurs with both. This is all done on a 64-bit server running Windows Server 2012R2. It was all working correctly until the VS2017 update sometime last week.
Back to top
View user's profile Send private message
John-Silver



Joined: 30 Jul 2013
Posts: 1400
Location: Aerospace Valley

PostPosted: Wed Jan 22, 2020 3:59 pm    Post subject: Reply with quote

Quote:
It was all working correctly until the VS2017 update sometime last week

- ah-ha a M$ tactic to get you to update to VS 2019 ! Wink ... and to infuriate developers like Silverfrost !
..... unless the problem also occurs using the VS 2019 plugin .
_________________
''Computers (HAL and MARVIN excepted) are incredibly rigid. They question nothing. Especially input data.Human beings are incredibly trusting of computers and don't check input data. Together cocking up even the simplest calculation ... Smile "
Back to top
View user's profile Send private message
Robert



Joined: 29 Nov 2006
Posts: 330
Location: Manchester

PostPosted: Wed Jan 22, 2020 10:52 pm    Post subject: Reply with quote

I have updated my Visual Studio 2017 to 15.9.19. The Fortran example 'Fortran Calculator' (At C:\Users\Robert\Documents\FTN95 Examples\NET\FortranCalculator\CS on my machine) compiles, links and runs fine. It creates an FTN95 assembly and calls it from C#.

What problem do you get -- and can you run the example?
Back to top
View user's profile Send private message Visit poster's website
j clark



Joined: 29 Mar 2008
Posts: 20
Location: Bala Cynwyd (Pennsylvania)

PostPosted: Fri Jan 24, 2020 1:14 pm    Post subject: Reply with quote

My problem is not with adding a reference to a C# project; it is with adding a reference to a FTN95 Application Extension project. I click on "References" under the project in Solution Explorer, then "Add" => "Add Reference" => "Browse" => navigate to the .dll I want, select it, click "Add" and VS2017 vanishes, instantly, completely. No messages, nothing.
Back to top
View user's profile Send private message
Robert



Joined: 29 Nov 2006
Posts: 330
Location: Manchester

PostPosted: Sun Jan 26, 2020 6:11 pm    Post subject: Reply with quote

I have reproduced this behaviour. It (for me) is specific to the 'Browse' feature. It will add recent assemblies or existing .NET ones quite happily.
Back to top
View user's profile Send private message Visit poster's website
Robert



Joined: 29 Nov 2006
Posts: 330
Location: Manchester

PostPosted: Tue Jan 28, 2020 12:43 am    Post subject: Reply with quote

This is a new plug-in DLL which should allow you to browse for DLL references:

http://www.silverfrost.com/public_downloads/beta/Ftn95Prj.dll

It should go here:

C:\Program Files (x86)\Silverfrost\Silverfrost FTN95 for Visual Studio
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group