VB.NET project works perfectly on windows 7. But when I run it in windows XP it doesn't run the way it should?

Question

0.00/5 (No votes)

See more:

What are the features in Visual Studio that might cause issues when running a project on Windows Xp.

I am writing a project. Well almost done, works perfectly fine on Windows 7. With Windows Xp, it just doesn't run most of my codes. I'm kinda lost, I don't know what is causing the issue.

I am using Visual Studio 2010.

okay, right now this part of the code is throwing errors on xp even after installing .net 4.

VB

Public Shared Function GetProcessorId() As String
        Dim strProcessorId As String = ""
        Dim query As New SelectQuery("Win32_processor")
        Dim search As New ManagementObjectSearcher(query)
        Dim info As ManagementObject
        For Each info In search.Get()
            strProcessorId = info("processorId").ToString()
        Next
        Return strProcessorId
    End Function

There has been a new development.
I found out that only one form is creating the problem for me.
That form includes two dll files. After adding them to the reference ( it was already added ), i checked if the dll files are present in the release folder, they are, I still got the same error. I know I'm wrong somewhere here. Would appreciate a lot if you guys can help me out.
The Error Message on loading the form:
" Retrieving the COM class factory for component with CLSID {CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} failed due to following error: 80040154 class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). "

Posted 24-Oct-13 8:04am

Tenzin Trullkhang

Updated 24-Oct-13 18:54pm

v4

Add a Solution

Comments

OriginalGriff 24-Oct-13 14:12pm

What do you mean "doesn't run most of my codes" - remember, we can't see your screen, or access your HDD so we are even more in the dark than you are! :laugh:

Use the "Improve question" widget to edit your question and provide better information.

Tenzin Trullkhang 24-Oct-13 23:46pm

Found out only one form is giving me problem. That form as two dll files. I included that in the reference, double checked in the release folder but still i'm getting the error messages. Updating the question with more details..

Ranjan.D 24-Oct-13 14:14pm

Oh boy you just need to target the framework version that's it.. what code you have written to break ? I'm kinda lost :laugh:

Tenzin Trullkhang 24-Oct-13 14:41pm

So, technically if I install the .NET framework 4 on the XP machine. My codes should work like how it runs on win7 ?? If that's the case then I believe the problem is deeper than I thought it is. :(

OriginalGriff 24-Oct-13 14:46pm

Depends what version of .NET you are using - i.e. what version you are targeting for your build. You only need to ensure that the version installed on XP is at least as high.
There is a simple way to check the current version installed:
http://www.codeproject.com/Tips/188674/A-safe-way-to-get-the-user-to-check-if-the-NET-fra
If you are targeting V3.0, and the machine has 4.0 then you are fine. To be honest, if you don't have the right version then your app shouldn't run at all! :laugh:

What errors is it throwing?

Tenzin Trullkhang 24-Oct-13 23:05pm

Sorry for the Delay, I went through your article. and the javascript:alert gave this
Mozilla/4.0 (compatible; MSIE8.0; Windows NT 5.1; Trident/4.0; NET 4C
Now I've coded it in NET 4.0.
For the top code, the error I'm getting is:
"
retrieving the COM class factory for component with CLSID {CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} failed due to following error: 80040154 class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
"

Sergey Alexandrovich Kryukov 24-Oct-13 20:30pm

Any opportunity to test it on XP?
—SA

Tenzin Trullkhang 24-Oct-13 23:06pm

Yeah. I have a VM setup.

Sergey Alexandrovich Kryukov 24-Oct-13 23:56pm

That's great. But then you can run it under the debugger and find out where the exception is thrown. The stack fragment shown is not very useful, as it shows exception propagation not in your code, which you, more importantly, did not show...
—SA

Tenzin Trullkhang 25-Oct-13 0:37am

what part of the code are you looking for?
I have the dll files in the same folder as the exe file, which runs fine on win7.

Sergey Alexandrovich Kryukov 25-Oct-13 0:44am

I'm not looking at any. You should know better. When exception is thrown (exception is thrown, not "error"), it happens in one single line of your code. And you show the fragment, not commenting one exact line in that code. That said, how do you know that exception was thrown there? If you knew that, you would know the exact line. Do you follow this logic?
—SA

Tenzin Trullkhang 25-Oct-13 0:52am

alright.. will get to handling those exception.. Thanks for pointing me in the right direction Sergey :)

Sergey Alexandrovich Kryukov 25-Oct-13 2:18am

You are welcome.
—SA

Tenzin Trullkhang 25-Oct-13 15:45pm

the activation form is giving the exceptions. Tried to catch the exception but I'm not successful.
I'm guessing I'll find better luck to code that part again in older version of VB and try running in WinXP.

Sergey Alexandrovich Kryukov 25-Oct-13 16:03pm

(Sigh...) Programming is never about luck, not at all... Just sorry for you...
—SA

Tenzin Trullkhang 25-Oct-13 16:22pm

More probability of it working??
No worries.. At least I got a direction yeah?? =)
Thanks again.. Checking with Mike Meinz, some dll with COM Object issue going on.. checking that possibility out..

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mike Meinz · Accepted Answer · 2013-10-24T08:53:00

Solution 1

Part I - Compile options
I don't have Visual Studio 2010. These instructions are for Visual Studio 2012. Sorry, I do not know if the same options settings are in Visual Studio 2010.
In My Project / Compile dialog
Select Target CPU = X86

In My Project / Application dialog
Select Target framework = .NET Framework 4 Client Profile
Check the Enable XP visual styles checkbox
In View Windows Settings, uncomment all of the <supportedos>...</supportedos> lines

Part II - References to a DLL that calls another DLL
In the project for the DLL that is calling the second DLL, the property sheet for the reference to the second DLL must have Copy Local set to False.

By having Copy Local = True in both the DLL project and the EXE project, you cause the second DLL to be included twice in the EXE project. Setting Copy Local set to False for the reference to the second DLL in the first DLL's project will fix that issue.

Posted 24-Oct-13 8:53am

Mike Meinz

Updated 27-Oct-13 2:18am

v5

Comments

Tenzin Trullkhang 24-Oct-13 23:21pm

In My Project / Compile dialog
* Target CPU = x86 already done
* Target Framework = .NET Framework 4 Client Profile already done

In My Project/Application dialog
* Enable XP visual style checkbox is already checked
* There's no target framework in application dialog
* Regarding the commenting of supportedos on the line above it, it says that
If your application is designed to work with Windows 7, uncomment the following supportedOS node. But I uncomment the line, built it and I still get the error:

" retrieving the COM class factory for component with CLSID {CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} failed due to following error: 80040154 class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)). "

Mike Meinz 25-Oct-13 8:34am

{CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} is a Windows WBEM component. It is not part of the .NET Framework. It is called by the .NET Framework. I checked on my Windows XP PC and it exists.

Is {CF4CC405-E2C5-4DDD-B3CE-5E7582D8C9FA} in the Windows XP registry HKEY_CLASSES_ROOT\CLSID hive?
Is the InprocServer32 value = C:\WINDOWS\system32\wbem\wmiutils.dll?

You mention adding DLL references and DLLs into the release folder?
What are those?
If these DLLs are related to Web-Based Enterprise Management (WBEM), they should not be put into your application's folder. You should use them in place in the C:\Windows\System32\wbem folder.

On your Windows XP PC, which service pack of Windows XP is it running? For the most compatibility, you should be running XP Service Pack 3. I created a VB .NET Console application that used your code. I ran it on both Windows 8 and Windows XP SP3 without problem. I added System.Management into My Project / References. The first line of my source code is Imports System.Management

Tenzin Trullkhang 25-Oct-13 14:51pm

Yeah, I imported the system.management
one of the dll file is to retrieve the machineID and another one to encrypt and decrypt.
on the VM im running win xp sp3.

I'm getting this when building my project :
"F:\New folder\Quiz_pro_ver0.1\Quiz_pro_ver0.1\Activation.vb(55) : warning BC42105: Function 'GetProcessorId' doesn't return a value on all code paths. A null reference exception could occur at run time when the result is used.
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): warning MSB3178: Assembly 'Ecnryptor.dll' is incorrectly specified as a file.
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): warning MSB3181: Two or more files have the same target path 'Ecnryptor.dll'.
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): warning MSB3178: Assembly 'MachineId.dll' is incorrectly specified as a file.
c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2580,9): warning MSB3181: Two or more files have the same target path 'MachineId.dll'.
Quiz_pro_ver0.1 -> F:\New folder\Quiz_pro_ver0.1\Quiz_pro_ver0.1\bin\Debug\Quiz_pro_ver0.1.exe
"

Mike Meinz 25-Oct-13 15:19pm

I think the problem might be that you added references to the DLLs that the .NET System.Management NameSpace classes call. You should not do that. If so, you should remove all DLL references from the project where .NET is the interface to the DLL.

Look in My Project / Publish / Application Files. Check "Show All Files". Make sure that there are no C:\Windows or C:\Windows subdirectory DLLs listed there. What is listed there? Please be specific.

Look in My Project / References What are the References listed there? Please be specific.

You mention adding DLL references and DLLs into the release folder?
What are those? Please be specific.

Tenzin Trullkhang 25-Oct-13 15:42pm

the two dll files are : MachineID.dll and Encryptor.dll. I referred some posts to get the machineID and to encrypt the ID to generate a product key.

I checked in MyProject/Publish/ApplicationFiles and the dll files are repeated, project.exe, project.exe.manifest, project.pdb and project.xml are listed.

Can you instruct me how to remove the COM objects? I'm quite new to VB. :)

Mike Meinz 25-Oct-13 15:48pm

Were MachineID.dll and Encryptor.dll created by you in another project? If so, what references are in those projects? If not, where did you get them?

You didn't answer all of my questions in detail so I still do not know the exact cause of your problem but expect that it is related to adding references to DLLs that should not have references. Did you add multiple references to MachineID.dll and Encryptor.dll?

Tenzin Trullkhang 25-Oct-13 16:24pm

one of the DLL is referring to another DLL (god!!)
getting rid of some codes.. (commenting them)..

Mike Meinz 26-Oct-13 4:44am

That is a big clue. I had to sleep on it to recognize it as a clue.

In the project for the DLL that is calling the second DLL, the property sheet for the reference to the second DLL must have Copy Local set to False.

By having Copy Local = True in both the DLL project and the EXE project, you cause the second DLL to be included twice in the EXE project. Setting Copy Local set to False for the reference to the second DLL in the first DLL's project will fix that issue.

Tenzin Trullkhang 27-Oct-13 3:43am

That Solved it!! :O Thank you So much Mike..
If you write the above solution as another solution I can Accept It.
It'll be benefit others as well.
Yet Again Thank you so much for your help and your patience =)
Tashi Delek!!!

Mike Meinz 27-Oct-13 7:30am

I updated Solution 1.

Tenzin Trullkhang 27-Oct-13 8:14am

Thank You =)

Mike Meinz 27-Oct-13 8:20am

Are you still having the problem with running on Windows XP or has that been resolved?

Tenzin Trullkhang 27-Oct-13 8:42am

i guess that dll file was the problem.. after installing .net framework 4 on the XP, I only had problem on one form. Now everything's working smooth.

Mike Meinz 27-Oct-13 9:44am

That's good!

Tenzin Trullkhang 25-Oct-13 16:18pm

I don't have any folders names INCLUDES.
I'm trying to get my first form to work without the dll files. Lets see if that solves it.