[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [TRNSYS-users] problem with new Type fortran code debugging in CVF



Ciao Stefano,

 

You should go to

 

Project/Settings

 

in Visual Studio and then choose the

 

Debug

 

tab.

 

Under “Executable for debug session”, make sure the reference to TrnsEXE.EXE is correct; typically, it should be

\Trnsys16\Exe\TRNExe.exe

 

If you installed TRNSYS 16.

 

If you installed it to \Program Files you may need to use “” around the path.

 

Good luck,

 

Werner

 


De : Avesani Stefano [mailto:stefano.avesani@eurac.edu]
Envoyé : vendredi 7 novembre 2008 12:54
À : trnsys-users@cae.wisc.edu
Objet : [TRNSYS-users] problem with new Type fortran code debugging in CVF

 

Dear all,

I'm trying to debug a Fortran TRNSYS new type code in order to find out wheter my Type works properly or not!

I get an error answer connected to the executable file (I have set the "Executable for debug session" as my MytypeXXX.dll in the Project setting).

 

In general: is the debugging of a new fortran code written for a new TRNSYS type creation possible (using the typical code structure of a TRNSYS type as explained in the manual!)?

 

I tried also with MVS 2005 and I got the following error "Visual Studio cannot debug because a debug target has not been specified".

 

Thanks for collaboration!!

Best regards

 

Stefano Avesani

 

Institute for Renewable energy


EURAC research
Viale Druso 1, I-39100 Bolzano

t +39 0471 055 345

f +39 0471 055 039

stefano.avesani@eurac.edu

www.eurac.edu 

 

This transmission is intended only for the use of the addressee and may contain confidential or legally privileged information.
If you receive this transmission by error, please notify the author immediately by mail and delete all copies of this transmission and any attachments.
Any use or dissemination of this communication is strictly prohibited by the "Privacy-Code", D.Lgs. 196/2003 and may conduct to penal prosecution and liability for damages.

 





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************