View previous topic :: View next topic |
Author |
Message |
j clark
Joined: 29 Mar 2008 Posts: 20 Location: Bala Cynwyd (Pennsylvania)
|
Posted: Sun Jan 19, 2020 8:27 pm Post subject: VS2017 Plugin Causes Crash? |
|
|
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 |
|
|
Robert
Joined: 29 Nov 2006 Posts: 446 Location: Manchester
|
Posted: Mon Jan 20, 2020 10:01 am Post subject: |
|
|
What version of Visual Studio do you have? |
|
Back to top |
|
|
j clark
Joined: 29 Mar 2008 Posts: 20 Location: Bala Cynwyd (Pennsylvania)
|
Posted: Mon Jan 20, 2020 1:42 pm Post subject: |
|
|
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 |
|
|
Robert
Joined: 29 Nov 2006 Posts: 446 Location: Manchester
|
Posted: Mon Jan 20, 2020 6:38 pm Post subject: |
|
|
Is it a .NET project and what sort of DLL? |
|
Back to top |
|
|
j clark
Joined: 29 Mar 2008 Posts: 20 Location: Bala Cynwyd (Pennsylvania)
|
Posted: Mon Jan 20, 2020 7:48 pm Post subject: |
|
|
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 |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Wed Jan 22, 2020 3:59 pm Post subject: |
|
|
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 ! ... 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 ... " |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 446 Location: Manchester
|
Posted: Wed Jan 22, 2020 10:52 pm Post subject: |
|
|
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 |
|
|
j clark
Joined: 29 Mar 2008 Posts: 20 Location: Bala Cynwyd (Pennsylvania)
|
Posted: Fri Jan 24, 2020 1:14 pm Post subject: |
|
|
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 |
|
|
Robert
Joined: 29 Nov 2006 Posts: 446 Location: Manchester
|
Posted: Sun Jan 26, 2020 6:11 pm Post subject: |
|
|
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 |
|
|
Robert
Joined: 29 Nov 2006 Posts: 446 Location: Manchester
|
|
Back to top |
|
|
|