Home > Software engineering >  VC how to invoke the.net framework development DLL
VC how to invoke the.net framework development DLL

Time:10-08

Recently developed a production test program, providing a DLL and VB examples, you can reference this DLL directly in VB, excuse me each expert, how to call it in VC, the trouble in details, thank you, first

Is willing to help please direct messages or QQ for example: 904307903. Rewards,

VB examples:
Reference MesInterFaceCombine. DLL

The Function MES_SaveResult (ByVal SerialNo used to As String, ByVal TestTime As DateTime, ByVal TestResult As String) As Boolean
Dim Model As New MesInterFace. Entity. The Entity
Dim ErrResult As String=""

Try
Model. The Panel=SerialNo used to
Model. The Operator=FrmSetSys. TxtOperator. Text. Trim
Model. The Resource=FrmSetSys. TxtProdNo. Text. Trim 'the machine number
Model. The Product=FrmSetSys. TxtProdName. Text. Trim
Model. The Workarea=FrmSetSys. TxtLineName. Text. Trim
Model. The Machine=FrmSetSys. TxtMachine. Text. Trim
Model. The Result=TestResult
Model. The TestTime=TestTime
Model. TestType=FrmSetSys. TxtStationName. Text. Trim
Model. OptType=MesInterFace. Enum. OptType. Trackin. ToString ()
Model. The ErrorMsg=Nothing
If MesInterFace. MesOpearteFun. MesMain (Model) Then
MessageBox. Show (" Success ")
Return False
The Else
For Each ErrMes As MesInterFace. Entity. The Error In the Model. The ErrorMsg
ErrResult +=the String. Format (" {0}, {1} ", ErrMes. ErrPanel, ErrMes. ErrMessage)
Next
MessageBox. Show (ErrResult)
Return False
End the If
Catch the ex As Exception
MessageBox. Show (ex. Message. ToString, "wrong!" , MessageBoxButtons. OK, MessageBoxIcon. Error)
Return False
End the Try
End Function

CodePudding user response:

A variety of invocation style
The CLR boarding
As a com component
C + +/CLI

CodePudding user response:

Deployment time also can give you a package to your vc program (exe and DLL),

CodePudding user response:

Don't be A language code is modified to B language code busywork,
Also don't use A language code to directly invoke B language code base, this complicated things so easy to get wrong,
Just make A, B language code of input and output is redirected to A text file, or modify A, B language code let it through text file input and output,
Can easily make A, B coordination between the two languages,
For example:
A will request data written to A file a.t xt, renamed after finish aa. TXT
B find aa. TXT, read its contents, call the corresponding function, and writes the results file b.t xt, after finish delete aa. TXT, changed its name to bb. TXT
Found A bb. TXT, read the content, after finish delete bb. TXT
Above can be replaced by any kind of A language or development environment, B can be replaced by any kind of with the development of A different language or development environment,
Unless A or B does not support to determine whether A file exists, file read and write and file name,
But who can name does not support to determine whether a file exists, file read and write and file name for the development of language or development environment?
Can put the temporary files on the RamDisk efficiency decrease wear disk,
Data structure is very complex, a text file format problems refer to a json or XML

The communication methods between the temporary text file sharing this process there are plenty of advantages, compared to other method only listed below I can think of now:
Loose coupling between process,
Can be on the same machine, process, also can cross machine, across the operating system, hardware platform, and even multinational,
, convenient debugging, and monitoring, only let the third party or artificial view the temporary text files,
Switch, convenient online service, need to delete or create the temporary text files,
, is convenient to realize distributed and load balancing,
Services to provide convenient, queue, queue is full and it is almost impossible to happen (unless the hard disk space full)
DE...

"Across different languages, machine, across the operating system, hardware platform, multinational, cross *. *" misery,
Back is "the use of Shared a plain text file information communication" of the shore!
  • Related