ChemAxon 60ee1f1328
17-08-2006 15:08:34
Hi,
I am interested to learn more about the statment in your recent news:
"Marvin 4.1 released. .NET support,"
Does this mean I can take the Marvin 4.1 Bean and treat as follows in order to use/import as a VS dll?
http://java.sun.com/j2se/1.4.2/
docs/guide/beans/axbridge/developerguide/index.html
Or perhaps you already generate the dll?
Is there any documentation ChemAxon provide on how to use Marvin Bean in ActiveX container context?
Cheers,
Daniel.
ChemAxon aa7c50abf8
17-08-2006 18:36:00
The .NET example in examples/ChemAxon.NET contains a flawed init.bat file. Please, replace it with the file I attached.
Peter
ChemAxon 60ee1f1328
28-09-2006 10:17:53
I have a few questions during set up...As usual thanks for any help...
1. regarding env var JNBRIDGE_BIN_DIR - no bin dir in the JNBridge runtime...does this refer to VS/sdk/v2.0/bin?
2. regarding env var MARVIN_JNB_PROXY_LIB_PATH - presumably wherever the marvin dll exist (root of the web app solution OK?)
3. Build.bat errors looking for csc.exe...I see this is in c:\windows\microsoft.net\framework\v2\csc.exe - how can I ensure this is visible to build.bat, another env var?
Cheers,
Daniel.
ChemAxon aa7c50abf8
29-09-2006 10:08:17
Hi Daniel,
Normally, you should not worry about those environment variables when setting up the example application.
Which Marvin version do you have. I suggest to get 4.1.1. A few bugs have been fixed in the example application of that version.
Cheers,
Peter
ChemAxon 60ee1f1328
29-09-2006 11:18:28
Hi Peter,
I am attempting to set up 4.1.1 I believe...
Well, I think they are being used by build.bat and are not set at any point before...I'll assume for now that my only issue is point 3 below...
Can you comment on point 3 of my questions below? i.e. build.bat cannot see csc.exe...
Cheers,
Daniel.
ChemAxon aa7c50abf8
02-10-2006 09:45:10
Hi Daniel,
Executing step 2. in section "Compile the source code into executable" (
http://www.chemaxon.com/marvin/examples/ChemAxon.NET/GUI/doc/index.html#compile) of the example setup description makes sure that csc.exe is visible in the current Command Prompt window:
Quote: |
Open a Command Prompt window and call the sdkvars.bat batch file located in the Bin directory of your .NET SDK installation to set the required environment variables. |
Cheers,
Peter