Turn off deprecated warnings?

  • Thread starter Thread starter marcwentink
  • Start date Start date
M

marcwentink

Is there a way to turn off depreacted warnings in Visual Studio 2005,
Professional Edition? I've got this VB project ported from version 2003
to 2005, I am a bit cautious to already changing the code that much
that it could not be ported back, but I got a few hundred warnings
saying things like:

'Public Function Add(parameterName As String, value As Object) As
System.Data.SqlClient.SqlParameter' is obsolete: 'Add(String
parameterName, Object value) has been deprecated. Use
AddWithValue(String parameterName, Object value).
http://go.microsoft.com/fwlink/?linkid=14202'

and a few warning between them I would really interested in.

The other frequent warnings I got are:

'Public Function GetPostBackEventReference(control As
System.Web.UI.Control) As String' is obsolete: 'The recommended
alternative is ClientScript.GetPostBackEventReference.

'Public Overridable Sub RegisterClientScriptBlock(key As String, script
As String)' is obsolete: 'The recommended alternative is
ClientScript.RegisterClientScriptBlock(Type type, string key, string
script).

Marc Wentink
 
Oh just give up will you.

Your incessant ramblings are becoming quite irritating. You are in no
way useful to these Groups what so ever - you are a hindrance.

I have been reading your posts and I am quite frankly disappointed that
someone who claims to have so much knowledge does nothing to help
others. Your posts portray you as an obnoxious, rude & stubborn
person.

Whether this is true or not we will never know - not that anyone in
these Groups would want to find out.
 
You probably want the #pragma that disables warnings if you are a good
boy/girl/martian and don't want to do global disables, but I am not
sure what the equivalent in VB is since I've only don this in c#.

There is a /nowarn VB.Net compiler option, but I do not know how to set
it.

I have also read that, in the project file, you can find a element like
this :
<NOWARN>... bring out your warning id #s here ...</NOWARN>
Putting the warning # you are getting in there should stop the rambling
:)

Here is a C# source (the bad code project ) for the #pragma option, if
it helps somehow :
http://www.codeproject.com/debug/pragma_tips.asp

// Andrew
 
listen ****er

you support a dead language; MS killed VB.net already

C# won the war; but I moved on to PHP a long time ago.

It just pisses me off-- and I hope that you all can learn from my
mistake and NEVER TRUST MICROSOFT.

WE HAD THE WORLDS MOST POPULAR LANGUAGE; AND MICROSOFT 'THREW THE GAME'

MICROSOFT 'TOOK A DIVE' AND KILLED VB.

-Aaron
 
Just go away. No one wants you in life and no one even wants you in a
forum. Must drive you crazy.
 
Andrew;

I'm so sorry that you're a junior programmer stuck in a dying language.

Personally; I want Microsoft to bring back VB6.

-Aaron
 
If you had read Andrew's previous post he actually uses C# - which, in
other posts, you have been praising and telling everyone and anyone
that C# is better than VB .NET and *far* more people use C# than ever
before.

Make up your mind - which is dead C#, VB.NET, ACCESS, PHP, VB6 the list
could go on and on.

On another note - why do insult everyone and throw the old "sorry
you're a junior programmer" at them.

I just do not understand people like you - I could lower myself to your
level however, I will refrain from falling so low.

Please just stop the annoying posts!
 
Barry, i think it's cute that he brings up vb6 as a non-dead language
:) It was great, thats for sure, but it's time has pased. I just hope
the OP gets a chance to read this and get the info I left.

In any case, thanks for coming back. I use C# personally (and in
previous jobs) but am using VB now. Not much difference between the
two in reality, but the main downside is that there isn't really
anything that VB is better at anymore. So why have two === languages?
Arr... who cares. I prefer C# because it's like C++, php and java,
all of which I must also know. Much less to worry about without yet
another syntax, thats all.
 
VB6 sure was great - still is in its own right. But VB .NET offers so
much more. Sure there are some annoying quirks but you can't tell me
VB6 didin't!! :-)

I see you're a man of many talents - although I guess in this day and
age developers need to be.

Hopefully this annoying idiot will stop posting soon - I don't know
where he has come from but I really hope he goes back very soon!
 
I would rather get ASS-RAPED then ever use a language named C-ANYTHING
or JAVA-ANYTHING

MS Somehow things that we accidently fell into VB and we did it because
we're jr programmers or something.

ITS NOT ****ING TRUE.

We've out-developed C++ fags and Java FAGS for about 15 years now. Just
because they finally made a decent IDE for C and JAVA _CRAP_ does that
mean that they need to kill THE WORLDS MOST POPULAR LANGUAGE?

-Aaron
 
Barry

VB.net (2002 and 2003) is DEAD it has already been killed. VB 2005?
It's too slow and buggy to be much use. It's too verbose; it crashes;
it's not the langauge I've used every day for the past 10 years.

C# is more popular... but on the other hand; I am incredibly defensive
of C# people coming in this newsgroup and fishing... and I'm defensive
here; because I've seen too many programmers that are stuck in an old
language that can't bother to learn a new language.

I believe that it would be in the best interests of everyone if MS
killed VB completely.

But because that's probably not going to happen-- then I will fight
every single person on this newsgroup until MS starts taking this
****ing language seriously.

Step #1 - give us a decent ****ing newsgroup NAME. VB 2005 isn't
called DOTNET so why is it in the newsgroup NAME?
Step #2 - rename VB 2007 to 'B#' or 'VB#' so that people see VB as
'trendy'
Step #3 - differentiate the products, VB 2005 is the same CRAP as C# is
Step #4 - give every single example in both C# and VB.net.
Step #5 - dont allow off-handed remarks like 'I cant translate this
like I dont use VB.net'
Step #6 - start laying a framework for TEN YEARS IN ADVANCE
Step #7 - give us the ability to use ONE LANGUAGE in all places--
simliar to what we had 5 years ago. Kill VBA macros... Replace it with
VB.net. Make DTS in SQL 2000 able to 'save package as VB 2005'
Step #8 - give us microsoft.com/vb
Step #9 - stop this asp.net postback CRAP and give us the ability to
write DHTML VbScript or VB 2005 ON THE CLIENT SIDE.
Step #10 - give us AJAX - in VB
Step #11 - either pay for all of our training; or dont make drastic
changes in a language WITHOUT REASON
Step #12 - stop trying to shove XML and OOP down our ****ing throats.


-Aaron
 
I do not have the time nor the inclination to continue this pointless
conversation.

You repeat the same things over and over - it's becoming quite comical.

It is clear that no-one shares your views and are taking no notice of
you. They are just bored and annoyed with your idiotic, abusive and
childish posts.

Why don't you create your own little Group call it whatever like and
ramble on to yourself - using your various names of course.

Maybe one day you will realise just how stupid you look/sound.


Regards
 
Name ONE FEATURE that I can't live without.

All I see is more verbosity; slower load times.. MORE COMPLEX
DEPENDENCIES

VB.net is not efficient until Microsoft pushes the .NET framework onto
every copy of windows ever.

they should come out with a security patch that requires the .NET
framework and just mandate that you need the .NET framework.

but before they do that; they need to fix this damn performance
problems.

Loading a simple VB 2005 app shouldn't take 20 seconds on a 2 ghz
machine with 2gb ram.

-Aaron
 
You aren't the sharpest knife, are you aaron. If you want to change
accounts to spam at least don't put "- Aaron" at the end.
 
Barry said:
I do not have the time nor the inclination to continue this pointless
conversation.

You repeat the same things over and over - it's becoming quite comical.

It is clear that no-one shares your views and are taking no notice of
you. They are just bored and annoyed with your idiotic, abusive and
childish posts.

Why don't you create your own little Group call it whatever like and
ramble on to yourself - using your various names of course.

Maybe one day you will realise just how stupid you look/sound.


Regards
Click to expand...
I fully agree. I think it's about time this fool stopped cluttering-up
this NG with his ramblings.

There's no doubt this schoolboy has some programming knowledge, but his
brattish behaviour has gone on for long enough. It was funny at first,
you could almost imagine the veins popping-out on his head as he was
writing, however his brattish behaviour has now worn very thin. (Who is
his father - John McEnroe?)

Take the tip Aaron, we're all laughing AT YOU, not with you!

ShaneO

There are 10 kinds of people - Those who understand Binary and those who
don't.
 
eat a dick bitch

and start standing up and complaining while MIcrosoft kills the worlds
most popular programming langauge

what a bunch of friggin WUSSES sitting around while your langauge DIES

MS will surely pull the plug soon

-Aaron
 
i'd rather be a broken record-- complaining about the death of vb--
then sit around another day; while you dipshits take a month to build
what used to take you a week.

'save the cheerleader, save the world'

-Aaron
 
Back
Top