dlx file from BlockStyler - integration in a VB projekt ?
dlx file from BlockStyler - integration in a VB projekt ?
(OP)
Hi- Does anyone know, if it should be possible to add the *.dlx file into a VB projekt ,and when the projekt is builded , the *.dlx file is Integrated in the *.dll .
I have tried to add the *. dlx file into the projekt as "add existing item" ,(VB 2010) but it seems to ,that it is not Integrated in the *.dll after buildning.
(The *. dlx is the menufile form NX Block styler. I think it will be nice if it could be integrated. Then should it not be nesseary to place the *.dlx file together with the *.dll file in the startup directory in NX. (When I execute the *.dll file from NX , I get an error , that the application cant find the *.dlx file.
Of coures when I place the *.dlx file in the direcotry , it Works.
lklo
I have tried to add the *. dlx file into the projekt as "add existing item" ,(VB 2010) but it seems to ,that it is not Integrated in the *.dll after buildning.
(The *. dlx is the menufile form NX Block styler. I think it will be nice if it could be integrated. Then should it not be nesseary to place the *.dlx file together with the *.dll file in the startup directory in NX. (When I execute the *.dll file from NX , I get an error , that the application cant find the *.dlx file.
Of coures when I place the *.dlx file in the direcotry , it Works.
lklo





RE: dlx file from BlockStyler - integration in a VB projekt ?
in the vb script has a line with the name ou dlx file. You can change to the full path of the dlx file.
Ex.:
theDialogName = "Sample.dlx"
theDialogName = "c:\temp\sampledir\Sample.dlx"
RE: dlx file from BlockStyler - integration in a VB projekt ?
thanks for your reply . Maybe I have not explained me very well ,
or maybee you are misunderstanding my question.
My intention is, if it is possible ?, to avoid using the the dlx file (menufile in user dirs startup/application folder).
This can only be done, if it can be merged together with the Vb file (journal) in the Building process in Visual Studio.
So the the resulting dll file can "standalone" in the user dirs startup/application folder.
lklo