Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Visual Web Developer 2005 Express SCREWS UP YOUR CODE on PURPOSE...STOP TOUCHING MY CODE, MICROSOFT!!!!

Reply
Thread Tools

Visual Web Developer 2005 Express SCREWS UP YOUR CODE on PURPOSE...STOP TOUCHING MY CODE, MICROSOFT!!!!

 
 
ik
Guest
Posts: n/a
 
      07-02-2004
DEAR MICROSOFT:

STOP TOUCHING MY CODE!!!!!!

Stop ADDING these attributes to my tags

meta:resourcekey="LiteralResource3"


Your Web Developer 2005 express added that crappy and unneeded attribute to
all my tags on my aspx page...you even added that attribute to the @page
directive. The people who actually do work might have to to bounce back to a
better HTML editor and NOT use 1.1 OR I don't even want that attribute in
the first place as I don't place to use .resx files anyway

DON'T DO THAT!!!

GOT IT!!!!!!


NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT TO USE
..NET 1.1

COMPRENDE!!!!!!!



 
Reply With Quote
 
 
 
 
Miha Markic [MVP C#]
Guest
Posts: n/a
 
      07-02-2004
Dear ik,

You might make a suggestion or report a bug instead of yelling and
crossposting in these newsgroups.
http://lab.msdn.microsoft.com/productfeedback/

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

"ik" <> wrote in message
news:ubGISw$...
> DEAR MICROSOFT:
>
> STOP TOUCHING MY CODE!!!!!!
>
> Stop ADDING these attributes to my tags
>
> meta:resourcekey="LiteralResource3"
>
>
> Your Web Developer 2005 express added that crappy and unneeded attribute

to
> all my tags on my aspx page...you even added that attribute to the @page
> directive. The people who actually do work might have to to bounce back to

a
> better HTML editor and NOT use 1.1 OR I don't even want that attribute in
> the first place as I don't place to use .resx files anyway
>
> DON'T DO THAT!!!
>
> GOT IT!!!!!!
>
>
> NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT TO

USE
> .NET 1.1
>
> COMPRENDE!!!!!!!
>
>
>



 
Reply With Quote
 
 
 
 
Simon Harvey
Guest
Posts: n/a
 
      07-02-2004
Good idea. They're actually very very responsive. Although I wouldnt shout
or they'll just think you're a physco - which undobtably you are...
But if we keep that between you an I we might get you perfectly reasonable
request fixed.

And remember, the products release date is a whole year away. I think the
product is remarkably mature given that fact

Simon


Dear ik,

You might make a suggestion or report a bug instead of yelling and
crossposting in these newsgroups.
http://lab.msdn.microsoft.com/productfeedback/

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com


 
Reply With Quote
 
Cowboy \(Gregory A. Beamer\) [MVP]
Guest
Posts: n/a
 
      07-02-2004
First, I have been around betas for quite some time and I can understand the
frustration. But, when you play with matches, you risk getting burned. If
you are working with original copies of production code in a beta
environment, you are taking an unnecessary risk. If you want to see what the
new product does, use a copy, then you do not have to worry about removing
things. If you are playing with production code, with no source control or
backup, you are making a mistake.

Second, when you rant about how dumb someone's methodology is, you are more
likely to be greeted with silence than have that person try to help you
through your difficulties. The louder you yell that someone is a jerk, the
less likely you are EVER going to get your problems solved. This is not a
Microsoft thing, but a human nature thing.

Third, if you feel you have a legitimate beef, register and log your
suggestion. It might surprise you to find out that the .NET team actually
read these things. You may find that there are reasons why certain things
are added, other than simply to screw up your code. You may still disagree
with them, but you will know the reasoning.

Fourth, this is a BETA product. BETAs are not the final release. This makes
point three especially germane. Log suggestions, as there is still time to
get changes for some things. If you have a problem, there may be others that
have the same problem. Also, BETA products may already have some changes in
mind.

Fifth, before installing and messing around with a product, especially a
BETA, you should read the readme files. They often contain a wealth of
information about known minefields. In a development product, the help files
are wonderful for understanding what it might do.

You are playing with a BETA, which is playing at your own risk. If you take
your prized breakables into a pre-school class, they will most likely get
broken. Instead of the Ming vase, take a copy.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
"ik" <> wrote in message
news:ubGISw$...
> DEAR MICROSOFT:
>
> STOP TOUCHING MY CODE!!!!!!
>
> Stop ADDING these attributes to my tags
>
> meta:resourcekey="LiteralResource3"
>
>
> Your Web Developer 2005 express added that crappy and unneeded attribute

to
> all my tags on my aspx page...you even added that attribute to the @page
> directive. The people who actually do work might have to to bounce back to

a
> better HTML editor and NOT use 1.1 OR I don't even want that attribute in
> the first place as I don't place to use .resx files anyway
>
> DON'T DO THAT!!!
>
> GOT IT!!!!!!
>
>
> NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT TO

USE
> .NET 1.1
>
> COMPRENDE!!!!!!!
>
>
>



 
Reply With Quote
 
clintonG
Guest
Posts: n/a
 
      07-02-2004
I have to concur -- the Express products are beta and thus still being
designed.

If people want to rant about corporate pigs they should start with shouting
to the world about AutoPimp (AutoDesk) which charges customers an
annual 'developer' fee just to obtain documentation required to learn how
to use the AutoCad products or to access their secret newsgroup(s).

--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL http://www.metromilwaukee.com/clintongallagher/



"Cowboy (Gregory A. Beamer) [MVP]" <> wrote in
message news:...
> First, I have been around betas for quite some time and I can understand the
> frustration. But, when you play with matches, you risk getting burned. If
> you are working with original copies of production code in a beta
> environment, you are taking an unnecessary risk. If you want to see what the
> new product does, use a copy, then you do not have to worry about removing
> things. If you are playing with production code, with no source control or
> backup, you are making a mistake.
>
> Second, when you rant about how dumb someone's methodology is, you are more
> likely to be greeted with silence than have that person try to help you
> through your difficulties. The louder you yell that someone is a jerk, the
> less likely you are EVER going to get your problems solved. This is not a
> Microsoft thing, but a human nature thing.
>
> Third, if you feel you have a legitimate beef, register and log your
> suggestion. It might surprise you to find out that the .NET team actually
> read these things. You may find that there are reasons why certain things
> are added, other than simply to screw up your code. You may still disagree
> with them, but you will know the reasoning.
>
> Fourth, this is a BETA product. BETAs are not the final release. This makes
> point three especially germane. Log suggestions, as there is still time to
> get changes for some things. If you have a problem, there may be others that
> have the same problem. Also, BETA products may already have some changes in
> mind.
>
> Fifth, before installing and messing around with a product, especially a
> BETA, you should read the readme files. They often contain a wealth of
> information about known minefields. In a development product, the help files
> are wonderful for understanding what it might do.
>
> You are playing with a BETA, which is playing at your own risk. If you take
> your prized breakables into a pre-school class, they will most likely get
> broken. Instead of the Ming vase, take a copy.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ************************************************
> Think Outside the Box!
> ************************************************
> "ik" <> wrote in message
> news:ubGISw$...
> > DEAR MICROSOFT:
> >
> > STOP TOUCHING MY CODE!!!!!!
> >
> > Stop ADDING these attributes to my tags
> >
> > meta:resourcekey="LiteralResource3"
> >
> >
> > Your Web Developer 2005 express added that crappy and unneeded attribute

> to
> > all my tags on my aspx page...you even added that attribute to the @page
> > directive. The people who actually do work might have to to bounce back to

> a
> > better HTML editor and NOT use 1.1 OR I don't even want that attribute in
> > the first place as I don't place to use .resx files anyway
> >
> > DON'T DO THAT!!!
> >
> > GOT IT!!!!!!
> >
> >
> > NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT TO

> USE
> > .NET 1.1
> >
> > COMPRENDE!!!!!!!
> >
> >
> >

>
>



 
Reply With Quote
 
ik
Guest
Posts: n/a
 
      07-05-2004
Nonsense. Microsoft went out of it's way to say for Whidbey and said over
and over again,

"We are not going to touch your code, Period"

And they did just that in the Beta.....

I don't care about the reasoning PERIOD. We, Me, Microsoft and real
developers out there already discussed this problem over and over again over
the years.

MICROSOFT, DON'T TOUCH THE CODE.




"Cowboy (Gregory A. Beamer) [MVP]" <> wrote
in message news:...
> First, I have been around betas for quite some time and I can understand

the
> frustration. But, when you play with matches, you risk getting burned. If
> you are working with original copies of production code in a beta
> environment, you are taking an unnecessary risk. If you want to see what

the
> new product does, use a copy, then you do not have to worry about removing
> things. If you are playing with production code, with no source control or
> backup, you are making a mistake.
>
> Second, when you rant about how dumb someone's methodology is, you are

more
> likely to be greeted with silence than have that person try to help you
> through your difficulties. The louder you yell that someone is a jerk, the
> less likely you are EVER going to get your problems solved. This is not a
> Microsoft thing, but a human nature thing.
>
> Third, if you feel you have a legitimate beef, register and log your
> suggestion. It might surprise you to find out that the .NET team actually
> read these things. You may find that there are reasons why certain things
> are added, other than simply to screw up your code. You may still disagree
> with them, but you will know the reasoning.
>
> Fourth, this is a BETA product. BETAs are not the final release. This

makes
> point three especially germane. Log suggestions, as there is still time to
> get changes for some things. If you have a problem, there may be others

that
> have the same problem. Also, BETA products may already have some changes

in
> mind.
>
> Fifth, before installing and messing around with a product, especially a
> BETA, you should read the readme files. They often contain a wealth of
> information about known minefields. In a development product, the help

files
> are wonderful for understanding what it might do.
>
> You are playing with a BETA, which is playing at your own risk. If you

take
> your prized breakables into a pre-school class, they will most likely get
> broken. Instead of the Ming vase, take a copy.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ************************************************
> Think Outside the Box!
> ************************************************
> "ik" <> wrote in message
> news:ubGISw$...
> > DEAR MICROSOFT:
> >
> > STOP TOUCHING MY CODE!!!!!!
> >
> > Stop ADDING these attributes to my tags
> >
> > meta:resourcekey="LiteralResource3"
> >
> >
> > Your Web Developer 2005 express added that crappy and unneeded attribute

> to
> > all my tags on my aspx page...you even added that attribute to the @page
> > directive. The people who actually do work might have to to bounce back

to
> a
> > better HTML editor and NOT use 1.1 OR I don't even want that attribute

in
> > the first place as I don't place to use .resx files anyway
> >
> > DON'T DO THAT!!!
> >
> > GOT IT!!!!!!
> >
> >
> > NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT TO

> USE
> > .NET 1.1
> >
> > COMPRENDE!!!!!!!
> >
> >
> >

>
>



 
Reply With Quote
 
Shawn B.
Guest
Posts: n/a
 
      07-16-2004
I'm not using the Express version, but I am using the Full VS.NET 2005 Beta
1 (Architect???) and I don't have see any problems with it messing up my
code. I'm particular about that so i would have noticed. I do not know
what would be different in the Express product. There is also, of course,
the fact that I may not be producing the same steps you are to "cause" such
an action but overall, I think its remarkably great of a product considering
it is pre-release material.


Thanks,
Shawn


"ik" <> wrote in message
news:...
> Nonsense. Microsoft went out of it's way to say for Whidbey and said over
> and over again,
>
> "We are not going to touch your code, Period"
>
> And they did just that in the Beta.....
>
> I don't care about the reasoning PERIOD. We, Me, Microsoft and real
> developers out there already discussed this problem over and over again

over
> the years.
>
> MICROSOFT, DON'T TOUCH THE CODE.
>
>
>
>
> "Cowboy (Gregory A. Beamer) [MVP]" <>

wrote
> in message news:...
> > First, I have been around betas for quite some time and I can understand

> the
> > frustration. But, when you play with matches, you risk getting burned.

If
> > you are working with original copies of production code in a beta
> > environment, you are taking an unnecessary risk. If you want to see what

> the
> > new product does, use a copy, then you do not have to worry about

removing
> > things. If you are playing with production code, with no source control

or
> > backup, you are making a mistake.
> >
> > Second, when you rant about how dumb someone's methodology is, you are

> more
> > likely to be greeted with silence than have that person try to help you
> > through your difficulties. The louder you yell that someone is a jerk,

the
> > less likely you are EVER going to get your problems solved. This is not

a
> > Microsoft thing, but a human nature thing.
> >
> > Third, if you feel you have a legitimate beef, register and log your
> > suggestion. It might surprise you to find out that the .NET team

actually
> > read these things. You may find that there are reasons why certain

things
> > are added, other than simply to screw up your code. You may still

disagree
> > with them, but you will know the reasoning.
> >
> > Fourth, this is a BETA product. BETAs are not the final release. This

> makes
> > point three especially germane. Log suggestions, as there is still time

to
> > get changes for some things. If you have a problem, there may be others

> that
> > have the same problem. Also, BETA products may already have some changes

> in
> > mind.
> >
> > Fifth, before installing and messing around with a product, especially a
> > BETA, you should read the readme files. They often contain a wealth of
> > information about known minefields. In a development product, the help

> files
> > are wonderful for understanding what it might do.
> >
> > You are playing with a BETA, which is playing at your own risk. If you

> take
> > your prized breakables into a pre-school class, they will most likely

get
> > broken. Instead of the Ming vase, take a copy.
> >
> > --
> > Gregory A. Beamer
> > MVP; MCP: +I, SE, SD, DBA
> >
> > ************************************************
> > Think Outside the Box!
> > ************************************************
> > "ik" <> wrote in message
> > news:ubGISw$...
> > > DEAR MICROSOFT:
> > >
> > > STOP TOUCHING MY CODE!!!!!!
> > >
> > > Stop ADDING these attributes to my tags
> > >
> > > meta:resourcekey="LiteralResource3"
> > >
> > >
> > > Your Web Developer 2005 express added that crappy and unneeded

attribute
> > to
> > > all my tags on my aspx page...you even added that attribute to the

@page
> > > directive. The people who actually do work might have to to bounce

back
> to
> > a
> > > better HTML editor and NOT use 1.1 OR I don't even want that attribute

> in
> > > the first place as I don't place to use .resx files anyway
> > >
> > > DON'T DO THAT!!!
> > >
> > > GOT IT!!!!!!
> > >
> > >
> > > NOW I HAVE TO GO AND REMOVE IT FOR ALL THE TAGS ON MY PAGE IF I WANT

TO
> > USE
> > > .NET 1.1
> > >
> > > COMPRENDE!!!!!!!
> > >
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Visual Web Developer 2005 and SQL Server Express 2005 Brad Brening ASP .Net 0 03-01-2007 04:28 PM
Visual Web Developer 2005 Express and SQL 2005 Express Jake Henderson ASP .Net Web Services 0 03-10-2006 10:18 PM
What is the difference between Visual Studio.NET 2005 ©MVisual Web Developer 2005 Express ad ASP .Net 5 04-04-2005 07:41 AM
HERE WE GO AGAIN, Visual Web Developer 2005 Express SCREWS UP YOUR CODE on PURPOSE...STOP TOUCHING MY CODE, MICROSOFT!!!! ik ASP .Net 8 07-09-2004 04:52 AM
Think twice before you install "Visual Web Developer 2005 Express Edition Beta1" on your developement machine. bredal Jensen ASP .Net 5 07-07-2004 10:58 AM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57