Prev: system library vulcan
Next: Pull in a MEF all of my edit windows close 2.8
From: Geoff Schaller on 6 Feb 2010 19:32
Hi Folks.

Tips and Tricks for Integrating Dot Net with VO #1

My developer workstation:

VS 2008 SP1
W7 Pro 64 bit
VO 2.8 SP3

....but then ALL the workstations in my office are now 64 bit and have
been for 2 years now but obviously I have clients with 32 bit OS from XP
to W7. So when we generate Dot Net executables we "usually" generate for
Any CPU and it works fine internally. Always has.

Except for VO apps running on some client 32 bit OS.
Here we find we must generate COM dlls for x86.

There is no problem for the 64 bit OS but for some reason there is a
RegASM issue in that the local GAC won't install the COM component
compiled for 'any cpu' on the 32 but OS. Crazily, it doesn't happen on
all PCs, just some. So something not installed or some patch missing or
whatever gives a problem. So, simply generate your COM dlls targeting
the x86 platform and your COM component will work on any PC with VO.

I'll have a demo of this ready to publish later next week.

Regards,

Geoff Schaller


From: Ginny Caughey on 6 Feb 2010 19:40
Hi Geoff,

You may find my paper useful on this topic;
http://www.elbe-data.se/sv/vografx/visualobjectsandcsharp.pdf


--

Ginny Caughey
www.wasteworks.com




"Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> wrote in message
news:OSnbn.6028$pv.5876(a)news-server.bigpond.net.au...
> Hi Folks.
>
> Tips and Tricks for Integrating Dot Net with VO #1
>
> My developer workstation:
>
> VS 2008 SP1
> W7 Pro 64 bit
> VO 2.8 SP3
>
> ...but then ALL the workstations in my office are now 64 bit and have been
> for 2 years now but obviously I have clients with 32 bit OS from XP to W7.
> So when we generate Dot Net executables we "usually" generate for Any CPU
> and it works fine internally. Always has.
>
> Except for VO apps running on some client 32 bit OS.
> Here we find we must generate COM dlls for x86.
>
> There is no problem for the 64 bit OS but for some reason there is a
> RegASM issue in that the local GAC won't install the COM component
> compiled for 'any cpu' on the 32 but OS. Crazily, it doesn't happen on all
> PCs, just some. So something not installed or some patch missing or
> whatever gives a problem. So, simply generate your COM dlls targeting the
> x86 platform and your COM component will work on any PC with VO.
>
> I'll have a demo of this ready to publish later next week.
>
> Regards,
>
> Geoff Schaller
>
>
From: Geoff Schaller on 6 Feb 2010 20:57
Hi Ginny.

Oh! ...now I wonder when that paper came about <g>.

Indeed. But as I mentioned, the things that confounded us for a while
was that 'Any CPU' still has some bugs with the generated classes. They
don't register on some 32 bit PCs whereas the x86 version installs on
all OS.

My sample is going to be about showing specific functionality. In
particular, Email and Reporting Services. I'll leave folks to read your
excellent paper on how to go about doing the C# side...

Cheers,

Geoff



"Ginny Caughey" <ginny.caughey.online(a)wasteworks.com> wrote in message
news:00e9e175$0$23822$c3e8da3(a)news.astraweb.com:

> Hi Geoff,
>
> You may find my paper useful on this topic;
> http://www.elbe-data.se/sv/vografx/visualobjectsandcsharp.pdf
>
>
> --
>
> Ginny Caughey
> www.wasteworks.com
>
>
>
>
> "Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> wrote in message
> news:OSnbn.6028$pv.5876(a)news-server.bigpond.net.au...
>
> > Hi Folks.
> >
> > Tips and Tricks for Integrating Dot Net with VO #1
> >
> > My developer workstation:
> >
> > VS 2008 SP1
> > W7 Pro 64 bit
> > VO 2.8 SP3
> >
> > ...but then ALL the workstations in my office are now 64 bit and have been
> > for 2 years now but obviously I have clients with 32 bit OS from XP to W7.
> > So when we generate Dot Net executables we "usually" generate for Any CPU
> > and it works fine internally. Always has.
> >
> > Except for VO apps running on some client 32 bit OS.
> > Here we find we must generate COM dlls for x86.
> >
> > There is no problem for the 64 bit OS but for some reason there is a
> > RegASM issue in that the local GAC won't install the COM component
> > compiled for 'any cpu' on the 32 but OS. Crazily, it doesn't happen on all
> > PCs, just some. So something not installed or some patch missing or
> > whatever gives a problem. So, simply generate your COM dlls targeting the
> > x86 platform and your COM component will work on any PC with VO.
> >
> > I'll have a demo of this ready to publish later next week.
> >
> > Regards,
> >
> > Geoff Schaller
> >
> >

From: Ginny Caughey on 7 Feb 2010 07:00
Hi Geoff,

My point (from the paper) is to always build for x86. Period. It's not only
COM-visible libraries that need this if they're built on a 64-bit machine
and run on a 32-bit machine.

Thanks for your suggestions for the paper btw.

--

Ginny Caughey
www.wasteworks.com




"Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> wrote in message
news:06pbn.6042$pv.2820(a)news-server.bigpond.net.au...
> Hi Ginny.
>
> Oh! ...now I wonder when that paper came about <g>.
>
> Indeed. But as I mentioned, the things that confounded us for a while was
> that 'Any CPU' still has some bugs with the generated classes. They don't
> register on some 32 bit PCs whereas the x86 version installs on all OS.
>
> My sample is going to be about showing specific functionality. In
> particular, Email and Reporting Services. I'll leave folks to read your
> excellent paper on how to go about doing the C# side...
>
> Cheers,
>
> Geoff
>
>
>
> "Ginny Caughey" <ginny.caughey.online(a)wasteworks.com> wrote in message
> news:00e9e175$0$23822$c3e8da3(a)news.astraweb.com:
>
>> Hi Geoff,
>>
>> You may find my paper useful on this topic;
>> http://www.elbe-data.se/sv/vografx/visualobjectsandcsharp.pdf
>>
>>
>> --
>>
>> Ginny Caughey
>> www.wasteworks.com
>>
>>
>>
>>
>> "Geoff Schaller" <geoffx(a)softxwareobjectives.com.au> wrote in message
>> news:OSnbn.6028$pv.5876(a)news-server.bigpond.net.au...
>>
>> > Hi Folks.
>> >
>> > Tips and Tricks for Integrating Dot Net with VO #1
>> >
>> > My developer workstation:
>> >
>> > VS 2008 SP1
>> > W7 Pro 64 bit
>> > VO 2.8 SP3
>> >
>> > ...but then ALL the workstations in my office are now 64 bit and have
>> > been
>> > for 2 years now but obviously I have clients with 32 bit OS from XP to
>> > W7.
>> > So when we generate Dot Net executables we "usually" generate for Any
>> > CPU
>> > and it works fine internally. Always has.
>> >
>> > Except for VO apps running on some client 32 bit OS.
>> > Here we find we must generate COM dlls for x86.
>> >
>> > There is no problem for the 64 bit OS but for some reason there is a
>> > RegASM issue in that the local GAC won't install the COM component
>> > compiled for 'any cpu' on the 32 but OS. Crazily, it doesn't happen on
>> > all
>> > PCs, just some. So something not installed or some patch missing or
>> > whatever gives a problem. So, simply generate your COM dlls targeting
>> > the
>> > x86 platform and your COM component will work on any PC with VO.
>> >
>> > I'll have a demo of this ready to publish later next week.
>> >
>> > Regards,
>> >
>> > Geoff Schaller
>> >
>> >
>
From: Geoff Schaller on 7 Feb 2010 16:48
Ah.

Then you might want to change all your VS images.
They all show Any CPU instead of x86 <g>.

Geoff


"Ginny Caughey" <ginny.caughey.online(a)wasteworks.com> wrote in message
news:001068fd$0$2018$c3e8da3(a)news.astraweb.com:

> Hi Geoff,
>
> My point (from the paper) is to always build for x86. Period. It's not only
> COM-visible libraries that need this if they're built on a 64-bit machine
> and run on a 32-bit machine.
>
> Thanks for your suggestions for the paper btw.
>
> --
>
> Ginny Caughey
> www.wasteworks.com

 |  Next  |  Last
Pages: 1 2
Prev: system library vulcan
Next: Pull in a MEF all of my edit windows close 2.8