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 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]

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==?=]

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]

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

[pmw]

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]

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

[pmw]

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.

--
pmw

[kimiraikkonen]

On Sep 23, 5:00*pm, pmw <pmw2...@gmail. comwrote:

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.

--
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

[pmw]

On 23 Sep., 17:12, kimiraikkonen <kimiraikkone.. [e-mail] e:

On Sep 23, 5:00*pm, pmw <pmw2...@gmail. comwrote:

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.

--
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

[pmw]

On 22 Sep., 15:00, pmw <[e-mail] 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

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

[kimiraikkonen]

On Sep 24, 2:43*pm, pmw <pmw2...@gmail. comwrote:

On 22 Sep., 15:00, pmw <[e-mail] 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

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.