VB.NET app compiled in Vista does not work on XP

**kimiraikkonen** · Sep 22 '08, 02:05 PM

Re: VB.NET app compiled in Vista does not work on XP

On Sep 22, 4:00 pm, pmw <we...@see64.ch wrote:

Hi
>
I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.
>
The thing is: I only have a virtual machine to test my software on XP,
but I can't develop on it.
>
The error shows up, when I try to declare a public OleDb object. Here
the source:
>
Public DatabaseConnect ion As New OleDb.OleDbConn ection
>
This error only happens, when I try to fill up the ConnectionStrin g of
this OleDb Object.
>
The error message itself is not really helpful, so I won't post it
right now.
>
My Question is: Where is the problem, is there someone which had
similar problem with Vista and XP apps?
>
Thank you for your help.
>
--
pmw

What's the error?

**PmW** · Sep 22 '08, 02:25 PM

Re: VB.NET app compiled in Vista does not work on XP

On 22 Sep., 16:04, kimiraikkonen <kimiraikkone.. .@gmail.comwrot e:

On Sep 22, 4:00 pm, pmw <we...@see64.ch wrote:
>
>
>
>
>

Hi

>

I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.

>

The thing is: I only have a virtual machine to test my software on XP,
but I can't develop on it.

>

The error shows up, when I try to declare a public OleDb object. Here
the source:

>

Public DatabaseConnect ion As New OleDb.OleDbConn ection

>

This error only happens, when I try to fill up the ConnectionStrin g of
this OleDb Object.

>

The error message itself is not really helpful, so I won't post it
right now.

>

My Question is: Where is the problem, is there someone which had
similar problem with Vista and XP apps?

>

Thank you for your help.

>

--
pmw

>
What's the error?- Zitierten Text ausblenden -
>
- Zitierten Text anzeigen -

Error Number 5 - The type initializer for
Project.ModuleG lobalVariables threw an exception

and the ex.InnerExcepti on.Message says: "Exception has been thrown by
the target of an invocation"

**kimiraikkonen** · Sep 22 '08, 03:55 PM

Re: VB.NET app compiled in Vista does not work on XP

On Sep 22, 5:16 pm, PmW <we...@see64.ch wrote:

On 22 Sep., 16:04, kimiraikkonen <kimiraikkone.. .@gmail.comwrot e:
>
>
>
>
>

On Sep 22, 4:00 pm, pmw <we...@see64.ch wrote:

>

Hi

>

I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.

>

The thing is: I only have a virtual machine to test my software on XP,
but I can't develop on it.

>

The error shows up, when I try to declare a public OleDb object. Here
the source:

>

Public DatabaseConnect ion As New OleDb.OleDbConn ection

>

This error only happens, when I try to fill up the ConnectionStrin g of
this OleDb Object.

>

The error message itself is not really helpful, so I won't post it
right now.

>

My Question is: Where is the problem, is there someone which had
similar problem with Vista and XP apps?

>

Thank you for your help.

>

--
pmw

>

What's the error?- Zitierten Text ausblenden -

>

- Zitierten Text anzeigen -

>
Error Number 5 - The type initializer for
Project.ModuleG lobalVariables threw an exception
>
and the ex.InnerExcepti on.Message says: "Exception has been thrown by
the target of an invocation"- Hide quoted text -
>
- Show quoted text -

Sorry, without seeing full code (if it's not too long), i can't make
out the reason beyond guessing the following:

1)Make sure you are using proper connection string syntax. Look at
http://www.connectionstrings.com for more info.

2)Try to put your code inside a Try-Catch block and catch the actual
error if it provides additional clue.
Like:

Try
'...All the code including connection string
' and stuff related to OleDb object
Catch ex As Exception
Msgbox(ex.Messa ge.ToString)
End Try

3)Try to initialize your disposable OleDb class within Using-End Using
to ensure there's no pending open connections.

All from me.

Hope this helps,

Onur Güzel

**Larry__Weiss** · Sep 22 '08, 09:25 PM

Re: VB.NET app compiled in Vista does not work on XP

Lets see if I got this right

compile on XP, run on XP is OK
compile on XP, run on Vista is OK
compile on Vista, run on Vista is OK
but, compile on Vista, run on XP is NOT OK

- Larry

pmw wrote:

Hi
>
I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.
>
The thing is: I only have a virtual machine to test my software on XP,
but I can't develop on it.
>
The error shows up, when I try to declare a public OleDb object. Here
the source:
>
Public DatabaseConnect ion As New OleDb.OleDbConn ection
>
This error only happens, when I try to fill up the ConnectionStrin g of
this OleDb Object.
>
The error message itself is not really helpful, so I won't post it
right now.
>
My Question is: Where is the problem, is there someone which had
similar problem with Vista and XP apps?
>
Thank you for your help.
>
--
pmw

**PmW** · Sep 23 '08, 06:05 AM

Re: VB.NET app compiled in Vista does not work on XP

On 22 Sep., 17:45, kimiraikkonen <kimiraikkone.. .@gmail.comwrot e:

>Sorry, without seeing full code (if it's not too long), i can't make
>out the reason beyond guessing the following:

Sorry, I would love to give you the source code, but I can't. Not
because it's big, I just can't hand you over that code.

>1)Make sure you are using proper connection string syntax. Look at http://www.connectionstrings.com for more info.

That one has to be allright, because on Vista it works with the same
one. I also checked it by creating an *.udl file on the XP machine to
create the string.

>2)Try to put your code inside a Try-Catch block and catch the actual r
>error if it provides additional clue. [...]

Already did that. There isn't really a good error message for that ...
makes it even harder to understand the problem.

>3)Try to initialize your disposable OleDb class within Using-End Using
>to ensure there's no pending open connections.

Problem 1: I can't use "Using-End Using" with "OleDB.OleDbCon nection".
Problem 2: I'm using the object all over the application, so it has to
be a public one, declared in a module. (like I'm doing it right now).

Thank you anyway for your help! I really appreciate that.

**PmW** · Sep 23 '08, 06:05 AM

Re: VB.NET app compiled in Vista does not work on XP

On 22 Sep., 23:19, Larry__Weiss <l...@airmail.n etwrote:

compile on XP, run on XP is OK

True

compile on XP, run on Vista is OK

Not sure, didn't try that. But I expect that it is running on Vista.

compile on Vista, run on Vista is OK

True

but, compile on Vista, run on XP is NOT OK

True

--
PmW

**dgcarter1949@googlemail.com** · Sep 23 '08, 08:05 AM

Re: VB.NET app compiled in Vista does not work on XP

On Sep 23, 7:01 am, PmW <we...@see64.ch wrote:

On 22 Sep., 17:45, kimiraikkonen <kimiraikkone.. .@gmail.comwrot e:>Sorry, without seeing full code (if it's not too long), i can't make

out the reason beyond guessing the following:

>
Sorry, I would love to give you the source code, but I can't. Not
because it's big, I just can't hand you over that code.
>

1)Make sure you are using proper connection string syntax. Look athttp://www.connections trings.comfor more info.

>
That one has to be allright, because on Vista it works with the same
one. I also checked it by creating an *.udl file on the XP machine to
create the string.
>

2)Try to put your code inside a Try-Catch block and catch the actual r
error if it provides additional clue. [...]

>
Already did that. There isn't really a good error message for that ...
makes it even harder to understand the problem.
>

3)Try to initialize your disposable OleDb class within Using-End Using
to ensure there's no pending open connections.

>
Problem 1: I can't use "Using-End Using" with "OleDB.OleDbCon nection".
Problem 2: I'm using the object all over the application, so it has to
be a public one, declared in a module. (like I'm doing it right now).
>
Thank you anyway for your help! I really appreciate that.

So you want help solving this problem but can't show us the code
that's causing it. Call me an old cynic, but that sounds like I've
got this homework please do it for me.

**PmW** · Sep 23 '08, 08:15 AM

Re: VB.NET app compiled in Vista does not work on XP

On 23 Sep., 10:05, "dgcarter1...@g ooglemail.com"
<dgcarter1...@g ooglemail.comwr ote:

On Sep 23, 7:01 am, PmW <we...@see64.ch wrote:
>
>
>
>
>

On 22 Sep., 17:45, kimiraikkonen <kimiraikkone.. .@gmail.comwrot e:>Sorry, without seeing full code (if it's not too long), i can't make

>out the reason beyond guessing the following:

>

Sorry, I would love to give you the source code, but I can't. Not
because it's big, I just can't hand you over that code.

>

>1)Make sure you are using proper connection string syntax. Look athttp://www.connections trings.comformo re info.

>

That one has to be allright, because on Vista it works with the same
one. I also checked it by creating an *.udl file on the XP machine to
create the string.

>

>2)Try to put your code inside a Try-Catch block and catch the actual r
>error if it provides additional clue. [...]

>

Already did that. There isn't really a good error message for that ...
makes it even harder to understand the problem.

>

>3)Try to initialize your disposable OleDb class within Using-End Using
>to ensure there's no pending open connections.

>

Problem 1: I can't use "Using-End Using" with "OleDB.OleDbCon nection".
Problem 2: I'm using the object all over the application, so it has to
be a public one, declared in a module. (like I'm doing it right now).

>

Thank you anyway for your help! I really appreciate that.

>
So you want help solving this problem but can't show us the code
that's causing it. Call me an old cynic, but that sounds like I've
got this homework please do it for me.- Zitierten Text ausblenden -
>
- Zitierten Text anzeigen -

Err ... yeah sure ...

So you want to know why I can't show you the code? First it is a
commercial product, so I can't just show you some source codes without
permission. Second, I'm working in a workplace where I have to go
through 4 security doors. So now you can imagine, that I'm not just
working at a standard workplace. Two good reasons, why I can't show
you the sources.

**Larry__Weiss** · Sep 23 '08, 09:05 AM

Re: VB.NET app compiled in Vista does not work on XP

pmw wrote:

I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.

Is there any way you can compare the IL code generated from the Vista
and XP compiled code?

- Larry

**pmw** · Sep 23 '08, 11:15 AM

Re: VB.NET app compiled in Vista does not work on XP

On 23 Sep., 10:59, Larry__Weiss <l...@airmail.n etwrote:

pmw wrote:

I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.

>
Is there any way you can compare the IL code generated from the Vista
and XP compiled code?
>
- Larry

There would be a way, if you can tell me how I can do that. Because I
don't know what you mean by "comparing IL code". It would be very nice
if you could help me.

--
pmw

**=?Utf-8?B?S2VycnkgTW9vcm1hbg==?=** · Sep 23 '08, 01:55 PM

Re: VB.NET app compiled in Vista does not work on XP

PmW,

Perhaps you could re-create the problem with a simple piece of code that did
not involve company secrets. You could then post that code.

A question: what techniques are you using to protect this commercial code
from being "de-compiled", since this is trivially easy to do with any code
written in .net or java?

Kerry Moorman

"PmW" wrote:

>
So you want to know why I can't show you the code? First it is a
commercial product, so I can't just show you some source codes without
permission. Second, I'm working in a workplace where I have to go
through 4 security doors. So now you can imagine, that I'm not just
working at a standard workplace. Two good reasons, why I can't show
you the sources.
>

**Larry__Weiss** · Sep 23 '08, 01:55 PM

Re: VB.NET app compiled in Vista does not work on XP

pmw wrote:

On 23 Sep., 10:59, Larry wrote:

>pmw wrote:

I've got a problem with my current application. I currently use
Windows Vista with Visual Studio Express 2008. If I compile the
application on Vista, it works fine on Vista, but it doesn't work on
XP. If I compile it on XP (with the same source code [copied from
vista]), it runs without any problems.

>>
>Is there any way you can compare the IL code generated from the Vista
>and XP compiled code?
>>

There would be a way, if you can tell me how I can do that. Because I
don't know what you mean by "comparing IL code". It would be very nice
if you could help me.
>

start by reading the instructions in

http://windowsclient.net/blogs/faqs/archive/2006/05/26/how-do-i-disassemble-a-net-assembly-into-il.aspx

the full usage spec for ildasm.exe is at

MSIL Disassembler (Ildasm.exe)

http://msdn.microsoft.com/en-us/library/f7dy01k1(VS.80).aspx

- Larry

**pmw** · Sep 23 '08, 02:05 PM

Re: VB.NET app compiled in Vista does not work on XP

On 23 Sep., 15:43, Kerry Moorman
<KerryMoor...@d iscussions.micr osoft.comwrote:

PmW,
>
Perhaps you could re-create the problem with a simple piece of code that did
not involve company secrets. You could then post that code.
>
A question: what techniques are you using to protect this commercial code
from being "de-compiled", since this is trivially easy to do with any code
written in .net or java?
>
Kerry Moorman
- Zitierten Text anzeigen -

Thats a good idea. I will try to recreate a similar project, which
uses the same objects.

This application is not for normal clients. It will only be used by
companies and people which do work in the same business. So they don't
even have interessts in getting the source code by decompiling it.
They can have it if they ask me.

--
wenga

**pmw** · Sep 23 '08, 02:05 PM

Re: VB.NET app compiled in Vista does not work on XP

On 23 Sep., 15:49, Larry__Weiss <l...@airmail.n etwrote:

start by reading the instructions inhttp://windowsclient.n et/blogs/faqs/archive/2006/05/26/how-do-i-disas...
>
the full usage spec for ildasm.exe is athttp://msdn.microsoft. com/en-us/library/f7dy01k1(VS.80) .aspx
>
- Larry- Zitierten Text ausblenden -
>
- Zitierten Text anzeigen -

Thank you very much, I will try this tomorrow and give you a feedback.

--
pmw

VB.NET app compiled in Vista does not work on XP

VB.NET app compiled in Vista does not work on XP

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment