Re: Stupefying Crazy and Insane

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

But ya know what Charlie, if we don't speak up about this crap, they
(Microsoft) will continue to think that everything is cool. I have
developed applications for years in DOS/Clipper/Foxpro and never had
to put up with this crap where:

1. The development environment no longer responds. I have a really
healthy PC, and this is unacceptable. God knows what Microsoft is
doing behind the scenes when I simply save a Change.

2. Intellisense was supposed to save us, but all it does is get in
way, and when you really need it, it ain't there? Go figure. I guess
if you had all the Methods and Properties memorized this would be a
cake walk.

3. Copy code from one form to another (ya know, object oriented
programming), but wait, you can't copy the form you just spent 10
hours developing, cuz that would break some Microsoft rule. I
continually reuse Foxpro forms simply by renaming them and changing
the important stuff. Do Microsoft .NET developers ever talk with
folks on the Foxpro side, cuz those Foxpro folks have it figured
out...

4. Spend hours on the phone with MS technical support only to figure
out that they don't have a clue how this stuff works either. Ya know,
complex databinding, and such. Jeez, I went thru two experts so they
would show me the way, and perhaps I enlightened them.

5. Develop the same forms with the same functionallity, and then
spend hours figuring out why one form works and another doesn't!
Cut, Copy and Paste just doesn't cut it! Not sure Why?

6. What kind of development environment would give you a message that
some Resource is no longer available and then die and trash your
entire 'Solution or Project'. Now theres a tool we all ought to
embrace.

7. Hilight a Function in Foxpro and it takes you to Help for that
exact function. Do the same in VB.net and wait for it to load
Internet help , which could take up to 5 minutes and include stuff I
did not ask for and have tried to turn off, and then wade thru all
this stuff I did not want. Setup your project and save it, and save
it somemore, and still you are faced with this Internet Help thing,
which is worthless.

8. I feel like I am in Microsoft.Office Hell. All this stuff you want
to turn off, but can't find out where its located. Its hidden in
some magical place and you will have to purchase a $50 book to get the
answers.

9. If your business is in a position to explore Open Source software
then do so. There are lots of great tools out there that are free. I
am not going to pay the price of an upgrade to Vista from XP. Ain't
going to happen. I am going to try and convince my company to stop
spending the big bucks and look at "Open Source".

10. Don't get me wrong, I will be a strong supporter of any software
environment that works, but Microsoft .NET simply doesn't cut it. We
are all waiting for the next verision that will solve all our
problems, and waiting.

Give me Borland or anyhting that works as intended and I will send my
development troops in that direction.

--Just me two cents









On Sat, 25 Nov 2006 03:15:36 -0600, "Charlie Tame" <charlie@xxxxxxxxx>
wrote:


"JJ" <NoEmailForMe...> wrote in message
news:de5fm29a5vlkgbfviregks45ifbcldodsh@xxxxxxxxxx
VS 2005 is an absolutely insane/ridiculous development environment.

Once you kinda figure out how things work, you get screwed...

IE,

Add a resource to your Project, ie test.png...
Add that resource to a form, ie, toolstripButton. Add a button with
its image set to the resource you just added. Now rename that
resource. Good-Bye toolStrip. Doesn't matter if you saved its former
self or not, its toast. Even more interesting is to add more than one
toolStrip and you will discover that All Of Them Are Toast..

We should use this development environment for all our enterprise
applications... Spend 4 hours on a form, then spend 4 more hours
because everyting is gone. Forget the fact that you save frequently
because this is such a piece of crap environmnet. Its toast... Start
over!

I can assume we will have to wait until VS3000 before we get a stable
development environment, then move to VS4000 which will change all
that because its not backward compatible.

I have always loved developing software, (Clipper/dBase/Visual Foxpro)
but now its a real struggle figuring out what does and doesn't work,
and what will make your project burnt toast, and lately it seems like
anything will make that happen.

I still have resources that display the wrong image, and this is after
repeated Builds, restarts, reboots. I guess the secret to this
environment is to decide what you need to do, then search for
knowledge base articles describing why this isn't a good idea or
offering work-arounds.

This development environment is almost like 2+2=4, but only on Fridays
on the 3rd week of September, and not a leap year.

There are also 200 books out there to help us thru this transition,
but most of them have misspellings that don't help at all, or I've
searched thru the index of the book for "BindingNavigator' or "Find"
and its not in the index.


It would appear that if you add 'One Line of Code', plan on spending
the next 8 hours figuring out why it doesn't work.


Hilarious, and I thought it was just because I am a really worthless
programmer. :)

At least next year is not a leap year so you should be okay for a little
while :)

Charlie

.

Quantcast