C# Windows Form Application with WCF on Windows XP

Question

0.00/5 (No votes)

See more:

Hi guys,

Just a quick question -

I have a Windows Form (C#) with a WCF reference built on VS 2008, Windows 7.
Everything works ok. The form connects to the service, gets the data I need, and outputs it to the form.

Once I deploy/move the application to a Windows XP Pro machine - nothing works!

I have 3.5, 3.0 and 2.0 frameworks installed with all the updates.

Has anyone had a similar issue before? Or knows what could be going wrong? Perhaps I need to release the app with all references inbuilt?

Thanks for your help!

Xav.

Posted 14-Jul-10 16:04pm

xavier9999

Add a Solution

4 solutions

Solution 4

Are you using WAS hosting? If so i guess it's not supported in XP

Posted 15-Jul-10 17:13pm

Ramin Tarhande

Comments

Nish Nishant 17-Jul-10 7:50am

Reason for my vote of 5
This is a fairly good suggestion/possible cause too. 5!

Solution 3

ive avoided the missing dll's by using a web reference rather than a web service...

apparently the web reference works with older systems.

The only problem I have now is - it takes sometimes up to 30 sec for the app to launch + run successfully. After the initial run, it only takes a second or so for it to fire!

Very strange : ( ~

Posted 15-Jul-10 12:41pm

xavier9999

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)

TheyCallMeMrJames · Accepted Answer · 2010-07-14T17:54:00

I ran into this and it was a third party DLL that was the problem (I think in that case it was the .Net MySQL library).

But, yes, if you've got all the frameworks in and patched, you're likely looking for a reference. Check the error you're getting/logging and if it's an assembly problem you should be able to spot it very quickly. You can either bake it in or just copy the DLL to the target machine to make it tick.

Cheers.

DaveyM69 · Accepted Answer · 2010-07-15T00:23:00

Solution 2

I ran into something similar the other night and it turned out there was an exception being thrown that was just being swallowed rather than crashing the app.

Wrapping all the WCF method calls in try/catch and displaying/logging the exception revealed my particular issue which was then easy to solve. (I should have done this from the beginning of course anyway! :doh: )

Posted 15-Jul-10 0:23am

DaveyM69