visual studio 2008 .net project with sql database

Question

0.00/5 (No votes)

See more:

VS2008

, +

I am new developer in .net , I have Project in vs2008 with mysql database

my problem is at Client side

1) when I use compiled EXE from project\bin\debug folder in windows 7 ultimate it runs properly but the same thing is not running in XP sp3 or sp2 computer.
2) the same EXE is running in Windows 7 professional , but giving error while opening any report forms (useing crystal report)
3) try to install crredist2008_x86 , but it dose not installed
4) try to install crredist2008_x86 by msiexec command forcefully then also it is not registering

after searching various options from net, done changes in reference property area , by "copy locally yes/no" and "specific version yes/no" but not worked

My request is, kindly give me the solution/step by step guide by which I can deploy standard EXE on any Operating System.

at Client side , first I install Mysql database with respective connectors, all frameworks , EXE
and Report folder.

Posted 19-Feb-13 5:58am

manipan

Add a Solution

Comments

manipan 21-Feb-13 22:43pm

Dear S.M.Ahsan Habib Thanks for your help
the said all 6 checkpoints I had done previousaly also, at client side I had also un-installed the anti-virus / firewall when standared procedure not worked.

Now, Yestarday the same situation I had created at my place on trial PC, only 4 steps work I had done
1) installed vcredist_x86
2) installed dotnetfx40_full_x86_x64
3) installed mysql-installer-community-5.5.28.3
4) installed my setup made from vs2008 setup project
just put Report folder manualy where the EXE situated in programfile folder after setup complited , and it works fine
above same things I had tried on Win-7 Professional ver. and XP sp3 ver. computer and just it works fine.
now lets see Today the same things work at client side, (only one more adivce I had get is to run CCcleaner or any other regcleaner to fix old unwanted issues which I ahd faced during installation on XP sp3)

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)

S. M. Ahasan Habib · Answer 1 · 2013-02-19T06:42:00

Some thing need to check
1) Make sure that both your development pc processor and deployment target has same processor architecture like 34/64 bit.
2) Make sure your project platform target is any cpu/x86/x64. When deployed your code to other machine, is that machine support that platform.
3) Make sure target machine has required .NET framework platform installed.
4) Make sure project dependent 3rd party components installed there.
5) Better you can use any installer project for deployment, tools like advance installer/windows installer. It will help you to deploy dependent component to target machine.
6) Make sure when you deploy code you use administrative privileged for deployment.