the file jversion.h is untracked and I forgot to change it
back to j805. Don't worry, it was built from the j805 branch,
and the version will be corrected when Eric builds anther
official release.
Ср, 19 апр 2017, Herbert Weissenbaeck // Privat написал(а):
> Same here.
> Works now. Can use it fr
Same here.
Works now. Can use it from C#. Thank you.
However JVERSION says J806(...). Why so?
Sent from my iPhone
> On 19 Apr 2017, at 13:24, David Mitchell wrote:
>
> Bill,
>
> I loaded the new j dll and redid the external registration with your new
> j.dll.
>
> The Excel com tests now wor
Bill,
I loaded the new j dll and redid the external registration with your new j.dll.
The Excel com tests now work with J805:
jopen
print jcmd("JVERSION")
Engine: j806/j32/windows
Beta: commercial/2017-04-19T23:40:20
Library: 8.05.14
Platform: Win 32
Installer: J805 install
InstallPath: c:/user
Thanks David for the insight.
I rebuilt the j805 j.dll again and uploaded to
www.jsoftware.com/download/jengine/j805-release/windows/j32
j_rebult2.dll
Only the typelib has changed, all other j engine source should
be the same as j805-release-a.
I tested it ok on vs2013 and vs2017. Hopefully the
Thank you. Interesting observation.
Any chance to get that fixed/patched in J805?
> On 18 Apr 2017, at 13:27, David Mitchell wrote:
>
> Folks,
>
> I tried some tests using Excel's com interface and j.dll from j602, j804,
> j805 and j64-806, all on Windows 10. I found these things.
>
> 1. The
Folks,
I tried some tests using Excel's com interface and j.dll from j602, j804, j805
and j64-806, all on Windows 10. I found these things.
1. The built-in registration with j602 ("%~dp0j.exe" /regserver) continues to
work. It registered j.exe and j.dll and I was able to use j.dll in Excel
I assume you are using c#.
Adding reference in vs is optional, wrapper class can also
be written by hand see jdllserverlib.cs in jwiki
* http://code.jsoftware.com/wiki/Guides/OLE_Server_for_CSharp
include jdllserverlib.cs into your source tab of project.
the proxy dll which contains auto generat
I installed vs2017 parallel to vs2013, adding reference failed in
both vs2013 and vs107. The situation was very confusing. Some
posts over the net said installation of vs2017 break windows
path for locating command line programs. I found a workaround is
to manually generate the proxy dll for j.dl
I'll check again, but I don't have vs2015. Development platform for J have
been standardized to vs2013.
On 15 Apr, 2017 7:46 pm, "Herbert Weissenbaeck // Privat" <
h...@herbertweissenbaeck.com> wrote:
> no success with vs 2015 and vs 2017.
> same error as before.
> have installed the new dll, un
no success with vs 2015 and vs 2017.
same error as before.
have installed the new dll, unregistered and re-registered with
syswow64\regsvr32.
Sent from my iPhone
> On 15 Apr 2017, at 07:17, Herbert Weissenbaeck // Privat
> wrote:
>
> Is there a chance to have the j805 j.dll re-built in a way
Is there a chance to have the j805 j.dll re-built in a way that makes it usable?
I need a functioning j.dll for serious work/calculations and would prefer not
to use a beta version but the latest stable release. Or is j806 beta considered
safe and stable enough?
Sent from my iPhone
> On 15 Apr
I rebuilt the 32-bit j805 j.dll and uploaded to
www.jsoftware.com/download/jengine/j805-release/windows/j32
It should be the same as the version release-a of 2017-02-26
and I have tested adding reference ok on vs2013.
please download j_rebuilt.dll and rename it to j.dll and let us
know if it also
There should be some mistake when building the j805 j.dll.
However j806 beta seems working again.
Пт, 14 апр 2017, Herbert Weissenbaeck // Privat написал(а):
> I tried to refer to the j.dll directly.
> VS tells me "A reference to (path...)\j.dll could not be added"
>
> i wonder, why j804 behave
I tried to refer to the j.dll directly.
VS tells me "A reference to (path...)\j.dll could not be added"
i wonder, why j804 behaves differently.
Sent from my iPhone
> On 14 Apr 2017, at 08:35, bill lam wrote:
>
> not sure why it can not add reference in vs. actually you don't have to
> add jd
not sure why it can not add reference in vs. actually you don't have to
add jdllserver to reference if you don't need intelligent sense.
On 14 Apr, 2017 7:57 pm, "Herbert Weissenbaeck // Privat" <
h...@herbertweissenbaeck.com> wrote:
> bill,
> thank you for your support.
> using syswow64/regsvr3
bill,
thank you for your support.
using syswow64/regsvr32 does not give any error message, confirms that the dll
is registered, but does not resolve my problem. the error message i receive
when trying to add the reference to J DLL Server in VS remains unchanged.
best
herbert
Sent from my iPhone
sorry, it should be syswow64
Пт, 14 апр 2017, bill lam написал(а):
> From your previous msg, it said
> 'C:\Program Files\j805\bin\j.dll'
>
> please check this is a J32 installation and have registered it
> using wow64/regsvr32.
>
> Чт, 13 апр 2017, Herbert Weissenbaeck // Privat написал(а):
> >
From your previous msg, it said
'C:\Program Files\j805\bin\j.dll'
please check this is a J32 installation and have registered it
using wow64/regsvr32.
Чт, 13 апр 2017, Herbert Weissenbaeck // Privat написал(а):
> I am actually compiling for 32bits (x86) only. (That's sufficient for this
> stage
I am actually compiling for 32bits (x86) only. (That's sufficient for this
stage of my development.)
Sent from my iPhone
> On 13 Apr 2017, at 22:22, bill lam wrote:
>
> 32-bit inproc server must be used with an 32-application.
> 32-bit out-of-process server can be used with either 32 or
> 64 a
32-bit inproc server must be used with an 32-application.
32-bit out-of-process server can be used with either 32 or
64 application. Please confirm what are the intended 32/64 bit
version of jdllserver and application (not visual studio).
jdllserver is in-proc server so that 32/64 bit must match,
Robert,
coincidentally I had the last Windows update just one hour ago; but the problem
was there before and after.
I am presently traveling and have no access to any other computer than my
notebook; thus I can not try to replicate my problem on another machine.
(I am using VS 2017 Enterprise
Herbert,
This may not be related at all, but is this recent? I read that Windows 10 had
the Creative update pushed on it in the last couple of days and if it was like
the last time it may break some things. Not sure why it would affect 805 and
not 804. ;-)
http://www.infoworld.com/article/318
Thank you. Tried to run vs as admin.
same result
uninstalled and re-installed j805 into users directory.
same (negative) result.
I can however use J EXE Server via COM also in the 805 version (but want J DLL
Server, which still gives me an error).
Any more ideas?
Sent from my iPhone
> On 13 A
I am not sure. IIRC It works for me. Perhaps it is a security issue. try
run visual studio as admin.
program files is protected, not sure if this is related to your problem.
On 14 Apr, 2017 7:48 am, "Herbert Weissenbaeck // Privat" <
h...@herbertweissenbaeck.com> wrote:
its regsvr32 without the
its regsvr32 without the "/r", i suppose.
in an admin console the registration seems to work. the J DLL Server (version
3) type library shows up in visual studio with file version 805. (the j804 one
showed file version 701.)
however selecting it gives an error: "A reference to 'J DLL Server (ve
typo, regsvr32
On 14 Apr, 2017 7:21 am, "bill lam" wrote:
> jdllserver should work for all versions. try open an admin command prompt
> at bin folder and type
> regvsr32 /r j.dll
>
> On 14 Apr, 2017 6:17 am, "Herbert Weissenbaeck // Privat" <
> h...@herbertweissenbaeck.com> wrote:
>
> On my Wind
jdllserver should work for all versions. try open an admin command prompt
at bin folder and type
regvsr32 /r j.dll
On 14 Apr, 2017 6:17 am, "Herbert Weissenbaeck // Privat" <
h...@herbertweissenbaeck.com> wrote:
On my Windows 10 machine J805 fails to register as a COM Server.
When I use jreg.cmd
On my Windows 10 machine J805 fails to register as a COM Server.
When I use jreg.cmd under 804 I get a "J DLL Server (version 3) Type Library"
in the kist of available Type Libraries in MS Visual Studio.
When I do the same with J805, no type library is registered.
Is this a bug or a feature? I
28 matches
Mail list logo
