[QUOTE=aldo;56645]Hello folks.
I just decompiled the aveva DLL assembly, that refers to database access and i got a little worried about what i've found. The source code about the most action methods (open methods like openproject, openmdb,etc...) are abstract, so you must implement it to works, i just don't know if its correct, because in the docs that came with the softer say's not so much about how to use the assembly itself, however, i tried to use it (not the decompiled source, the DLL itself) and just got the same error using those action methods (NULL EXCEPTION was raised), i guess its about the abstract methods... if its true, that's no aveva code that works for this (Open a project, connect to database,...), if u must implement it, it's something like having nothing of help for this.
If some have some direction to guide me, i'll really apreciate it.
Anyway best regards to everyone.
its correct to implement abstract methods, but i'm intresting what exact you did in you code?
can you post some code in this thread? or post to my PM
I have the PDF
Net Customisation User Guide.pdf
but I can not find the
Net Interface Reference Files.zip file.
the pdf was in the manuals /documentation folder..
searched for the zip and find nothing.
The Net Interface Reference Files.zip file should place at same location as Net Customisation User Guide.pdf.
If it is not there.. it might has been deleted or someone miss deleted or it not install properly..
my suggestion is you refer to your nearest AVEVA Office and ask for that particular file.
Hi Did anyone attend the workshop descibed at the begining of the thread? If so was it good? Please chew on the content of the workshop a bit!
Has anyone any tips on debugging using addins? -E.g. Load addin at runtime and trace code line by line?
Tips on debugging for pml.net?
How to unload a pml.net object to be able to recompile and try it agin without restarting PDMS?
Do you have any tips on PdmsStandalone? We would like to create a 100%
C# plugin, in order to use debug, create unit test without loading the generated dll for each test .
We also tested all example in Sample.zip.
Below you can find a sample code in C# that we would like to work :) :
One extra requirement with standalone applications is that you need to be sure that all necessary environment variables are set. The evars.bat script does this when running the main applications. In particular if the SAM and MAS project variables are not set then you will not be able to open the Sample (SAM) project.
[QUOTE=agsmith;66777]One extra requirement with standalone applications is that you need to be sure that all necessary environment variables are set. The evars.bat script does this when running the main applications. In particular if the SAM and MAS project variables are not set then you will not be able to open the Sample (SAM) project.