469,626 Members | 1,774 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,626 developers. It's quick & easy.

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

pmw
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 DatabaseConnection As New OleDb.OleDbConnection

This error only happens, when I try to fill up the ConnectionString 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
Sep 22 '08 #1
19 4056
On Sep 22, 4:00*pm, pmw <we...@see64.chwrote:
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 DatabaseConnection As New OleDb.OleDbConnection

This error only happens, when I try to fill up the ConnectionString 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?
Sep 22 '08 #2
PmW
On 22 Sep., 16:04, kimiraikkonen <kimiraikkone...@gmail.comwrote:
On Sep 22, 4:00*pm, pmw <we...@see64.chwrote:


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 DatabaseConnection As New OleDb.OleDbConnection
This error only happens, when I try to fill up the ConnectionString 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.ModuleGlobalVariables threw an exception

and the ex.InnerException.Message says: "Exception has been thrown by
the target of an invocation"
Sep 22 '08 #3
On Sep 22, 5:16*pm, PmW <we...@see64.chwrote:
On 22 Sep., 16:04, kimiraikkonen <kimiraikkone...@gmail.comwrote:


On Sep 22, 4:00*pm, pmw <we...@see64.chwrote:
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 DatabaseConnection As New OleDb.OleDbConnection
This error only happens, when I try to fill up the ConnectionString 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.ModuleGlobalVariables threw an exception

and the ex.InnerException.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.Message.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
Sep 22 '08 #4
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 DatabaseConnection As New OleDb.OleDbConnection

This error only happens, when I try to fill up the ConnectionString 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
Sep 22 '08 #5
PmW
On 22 Sep., 17:45, kimiraikkonen <kimiraikkone...@gmail.comwrote:
>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.OleDbConnection".
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.

Sep 23 '08 #6
PmW
On 22 Sep., 23:19, Larry__Weiss <l...@airmail.netwrote:
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
Sep 23 '08 #7
On Sep 23, 7:01*am, PmW <we...@see64.chwrote:
On 22 Sep., 17:45, kimiraikkonen <kimiraikkone...@gmail.comwrote:>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.connectionstrings.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.OleDbConnection".
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.
Sep 23 '08 #8
PmW
On 23 Sep., 10:05, "dgcarter1...@googlemail.com"
<dgcarter1...@googlemail.comwrote:
On Sep 23, 7:01*am, PmW <we...@see64.chwrote:


On 22 Sep., 17:45, kimiraikkonen <kimiraikkone...@gmail.comwrote:>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.connectionstrings.comformore 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.OleDbConnection".
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.
Sep 23 '08 #9
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
Sep 23 '08 #10
pmw
On 23 Sep., 10:59, Larry__Weiss <l...@airmail.netwrote:
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
Sep 23 '08 #11
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.
Sep 23 '08 #12
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/...y-into-il.aspx

the full usage spec for ildasm.exe is at
http://msdn.microsoft.com/en-us/libr...k1(VS.80).aspx

- Larry
Sep 23 '08 #13
pmw
On 23 Sep., 15:43, Kerry Moorman
<KerryMoor...@discussions.microsoft.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
Sep 23 '08 #14
pmw
On 23 Sep., 15:49, Larry__Weiss <l...@airmail.netwrote:
start by reading the instructions inhttp://windowsclient.net/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
Sep 23 '08 #15
pmw
On 23 Sep., 15:43, Kerry Moorman
<KerryMoor...@discussions.microsoft.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.

--
pmw
Sep 23 '08 #16
On Sep 23, 5:00*pm, pmw <pmw2...@gmail.comwrote:
On 23 Sep., 15:43, Kerry Moorman

<KerryMoor...@discussions.microsoft.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.

--
pmw
Pmw,
You can also consider re-building project and and starting a new
project from the scratch and create all the source code files manually
(files that are in solution explorer) by right clicking solution
explorer -add -new item, then copy-paste the required codes from
your previous (problematic one) project into the new one.

Plus, if you're using settings file (My.Settings) you can re-create it
for the possibility of corruption.

Worth to try.

HTH,

Onur Güzel
Sep 23 '08 #17
pmw
On 23 Sep., 17:12, kimiraikkonen <kimiraikkone...@gmail.comwrote:
On Sep 23, 5:00*pm, pmw <pmw2...@gmail.comwrote:


On 23 Sep., 15:43, Kerry Moorman
<KerryMoor...@discussions.microsoft.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.
--
pmw

Pmw,
You can also consider re-building project and and starting a new
project from the scratch and create all the source code files manually
(files that are in solution explorer) by right clicking solution
explorer -add -new item, then copy-paste the required codes from
your previous (problematic one) project into the new one.

Plus, if you're using settings file (My.Settings) you can re-create it
for the possibility of corruption.

Worth to try.

HTH,

Onur Güzel- Zitierten Text ausblenden -

- Zitierten Text anzeigen -
I just now tested the OleDB object with a different, prototype
project. I don't have any problems there. It might be that the current
project is damaged. I will now try to copy the sources to a new
project. I hope it's going to help.

I will report back.

--
pmw
Sep 24 '08 #18
pmw
On 22 Sep., 15:00, pmw <we...@see64.chwrote:
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 DatabaseConnection As New OleDb.OleDbConnection

This error only happens, when I try to fill up the ConnectionString 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
Problem solved! It really was a damaged project file. Copied now all
the sources to a complete new project, and now it works ... don't ask
me why.

Thank you all very much for your help!

--
pmw
Sep 24 '08 #19
On Sep 24, 2:43*pm, pmw <pmw2...@gmail.comwrote:
On 22 Sep., 15:00, pmw <we...@see64.chwrote:


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 DatabaseConnection As New OleDb.OleDbConnection
This error only happens, when I try to fill up the ConnectionString 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

Problem solved! It really was a damaged project file. Copied now all
the sources to a complete new project, and now it works ... don't ask
me why.

Thank you all very much for your help!

--
pmw- Hide quoted text -

- Show quoted text -
Cool. Thanks for the feedback, glad you solved.

Onur G.
Sep 24 '08 #20

This discussion thread is closed

Replies have been disabled for this discussion.

By using this site, you agree to our Privacy Policy and Terms of Use.