|
I've never created a proxy that way. The way I have done it successfully is to run the WSDL command line tool to generate a CSharp file containing the proxy class. I then add this file to a Class Library ( Assembly ) project. The resulting assembly can be added as a reference to any number of projects and used assuming you account for any changes is the address ( URI ) to the hosted Web Service.
led mike
|
|
|
|
|
This would work fine too...only thing is I'd have to re-run wsdl if I added another method to the web service. It' really just a few more steps, but it would be nice to avoid them if I could.
If I ever dig anything up on why it's not working as expected, I'll be sure to post the solution to this thread.
|
|
|
|
|
Hi everybody,
I have two editions of Visual Studio.NET - 2003 and 2005. Of course both of them come with the different editions of the MSDN library. To conserve space on my hard drive, i'm considering uninstalling MSDN Library for Visual Studio.NET 2003 since the 2005 edition is present. What d'you think? Do i go ahead?
Obinna from Nigeria.
//obinnaaj Eof
|
|
|
|
|
I would get rid of both, unless you use them heavily. It's all available on-line anyway.
Simon
|
|
|
|
|
Simon Stevens wrote: It's all available on-line anyway.
Only problem is you lose context-sensitive help. However, this has become less reliable these days. Plus you can also get it by hooking up that Google Search macro to MSDN online.
Kevin
|
|
|
|
|
I did this in my last contract when I got a new PC and had to install both VS's from scratch. I just installed VS 2005 help and set VS 2003 to point to VS 2005 Help. Worked OK.
Kevin
|
|
|
|
|
That is what I have done with my VS installs. I have VS2003, VS2005, VS2008, and I just have VS2008 MSDN Documentation installed. I did this because the documentation still says which .NET framework everything works for.
Regards,
Thomas Stockwell
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Visit my homepage Oracle Studios[ ^]
|
|
|
|
|
I am working on an application that requires the Help forms that are commonly seen in a windows application, but I do not have any idea how to go about it. I believe that there is some module somewhere in Visual Studio .NET to do it. There are three tab strips composed of: Contents, Index and Find. The Contents tab strip has expandable and collapsible menu items. The Index tab strip provides the ability to search through all of the Help items in the Contents tab strip. I tried to find an article on the subject, but I could not find anything on it. Could someone kindly point me toward the correct resource or article on how to get started?
|
|
|
|
|
|
What you need is Microsoft's HTML Workshop.
Regards,
Thomas Stockwell
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Visit my homepage Oracle Studios[ ^]
|
|
|
|
|
Hi to all i am a beginer of dotnet flatform,current do a attendens project in a small compahy...in chennai...how to create employeelist in windows application..
|
|
|
|
|
turailakshmanan wrote: i am a beginer of dotnet flatform,current do a attendens project in a small compahy
Beginners should be studying (student) Computer Science not doing projects in companies. You start with a general foundation in Computer Science and then more specific studies of Computer Programming. Once you have obtained minimal understanding you become an intern in a company where you study again under the supervision of experienced programmers. They would answer these types of questions for you.
Who ever told you that you don't need to study Computer Science to be a programmer was wrong.
Good luck.
led mike
|
|
|
|
|
led mike wrote: Beginners should be studying (student) Computer Science not doing projects in companies. You start with a general foundation in Computer Science and then more specific studies of Computer Programming. Once you have obtained minimal understanding you become an intern in a company where you study again under the supervision of experienced programmers. They would answer these types of questions for you.
Who ever told you that you don't need to study Computer Science to be a programmer was wrong.
Well I didn't study CS. I studied pottery and comparative literature in the Kotohoshi Indians.
And yes - my previous sentences are complete crap.  If you want a career as a programmer, you need to start studying and then never stop - for the rest of your life.
|
|
|
|
|
turailakshmanan wrote: flatform
turailakshmanan wrote: urrent do a attendens project in a small compahy
Please Please do a favor to us, attend some evening classes that teaches basic English to kindergarten students.
turailakshmanan wrote: how to create employeelist in windows application..
There is something called a search engine[^].
"Sometimes the greatest journey is the distance between two people" - Nice quote from a Nice Indian Movie
|
|
|
|
|
I thought these were merely syntactical sugar offered by the 3.5 compiler, but would compile down to normal getters and setters that would work on the 2.0 framework. Yes, when I try and ‘down-grade’ a 3.5 project to 2.0, I get compiler errors for automatic properties. Is this just something I have to live with, or is there another way?<o:p>
|
|
|
|
|
Brady Kelly wrote: I thought these were merely syntactical sugar offered by the 3.5 compiler, but would compile down to normal getters and setters that would work on the 2.0 framework.
Interesting. Do you have an URL to something that says that?
led mike
|
|
|
|
|
|
Well first none of those URLs is "Documentation". Second I can't find any form of the phrase "down grade" in any of them so they don't seem to say what you are saying you think should happen. So what documentation did you read that made you believe that it would work that way?
Brady Kelly wrote: when I try and ‘down-grade’ a 3.5 project to 2.0
led mike
|
|
|
|
|
I thought you meant links to support my statement that automatic properties are syntactic sugar. Bert Smal, the first link, is a well regarded blogger and has quite a good explanation.
My downgrade issue is not that I thought everything would work when I downgraded, it's just something I tried, and I knew it would fail initially because of all the 'using Linq' statements, but I didn't think would fail on automatic properties because I didn't know changing the target changed the compiler. A replier on the DOTNET-CLR list tells me this can actually be done, but not in my scenario:
"I've used automatic properties happily from the 3.0 compiler to generate a 2.0 assembly and see no issue with that. Same goes with extension methods (provided you add a fake attribute in your class). <o:p> Of course you need to *target* 2.0 using the msbuild and compiler shipping in 3.5, otherwise it won't work." - Sebastien Lambla [seb@SERIALSEB.COM]
Pits fall into Chuck Norris.
|
|
|
|
|
Brady Kelly wrote: Of course you need to *target* 2.0 using the msbuild and compiler shipping in 3.5, otherwise it won't work."
Thanks Brady, I'm still using 2.0 and VS2005 so this is all very helpful to me when I move to 3.5 and VS2008 which I believe will be soon. 
led mike
|
|
|
|
|
You'll love it! There are many new and fun ways to avoid writing code. 
Pits fall into Chuck Norris.
|
|
|
|
|
Brady Kelly wrote: There are many new and fun ways to avoid writing code.
You could always go work at McDonalds to avoid writing code. 
led mike
|
|
|
|
|
Actually I'm studying Law.
Pits fall into Chuck Norris.
|
|
|
|
|
I now actually have code that says that. The following code compiles and runs targeting 2.0:
class Program
{
static string MyName { get; set; }
static DateTime MyDob { get; set; }
static void Main(string[] args)
{
MyName = "Brady Kelly";
MyDob = new DateTime(1969, 12, 13);
Console.WriteLine(MyName);
Console.WriteLine(MyDob.ToString());
}
}
Pits fall into Chuck Norris.
|
|
|
|
|
They are syntactic sugar. When you downgrade a 3.5 project to 2.0, you get the C# 2.0 compiler which doesn't understand them.
Calling it ".NET 3.5" made people expect that there was a new runtime. There isn't. The CLR is still version 2.0.50727 (although SP1 is required). Windows Forms is unchanged. .NET 3.0 was pure extensions, "3.5" ships with service packs for .NET 2.0 and WinFX.NET 3.0 to add a few new features to the assemblies which shipped in those versions.
As long as you don't use any of the new ".NET 3.5" libraries, or compiler features which require runtime support in the new libraries (e.g. LINQ), your code will still run against .NET 2.0, even if you're 'targeting' .NET 3.5.
Visual Studio 2008's "multi-targeting" is a sham. It's really targetting the same runtime throughout. It doesn't offer the ability to target .NET 1.1, which would have been really useful.
DoEvents: Generating unexpected recursion since 1991
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
