That granted but Visual Basic intellisense hasn't always been the best. The level of background compilationcompliation feedback is very good in the SP1 update, so much so even VB developers should notice the difference.jh71283 said:I take it you're a C# dev? VB has had this for yrs...
Anyone enjoying the red squiggly lines that appear in the code editor in VS2008? I think I've saved a month already in not building projects that were destined to fail, but the background compilation caught.
Using dynamic languages really is walking a tightrope without a safety net. Or people that love Ducatti motorcyles, that go 200 miles an hour - saying, "the faster I went, the wider the road became".
That (in some ways - and not exclusively) is dynamic languages. It must take ages to fix simple bugs, when you rely on late binding and all that meta-programming malarkey.
10 out of 10 for a real time saver in .NET 3.5 SP1.
Absolutely useless error message, sometimes it can be in a completely different form.
wrap a try catch block around the Application.Run(new Form1()); and catch the exception there
then MessageBox.Show(ex.message, ex.source);
That should point you to where the problem is.The only thing to remember is the problem is usually not where you think it is, and you will have made a bad coding error.
JChung2006 said:vesuvius said:*snip*
IE 8 is a legitimate player once again though, Despite the naysayers, who, to be blunt, have history (browser wars and the abandonment of IE 6) on their side, I have high hopes that IE 9 will achieve CSS 3 and HTML 5 compliance. That is, once those standards get finalized. Get 'er done, W3C!
There's one nagging question that bothers me. How aggressively will Microsoft encourage users to upgrade from previous versions? If they're wishy-washy about doing that, then IE 8, as great a technical feat as it might be, will be all for naught as users will continue to use whatever browser they're running. Microsoft likes to focus on their competitors, but, as Vista and its ongoing battle against stalwart XP demonstrated, perhaps we need to focus more on convincing people that IE8 is better than IE7 and IE6. The biggest blocker to Vista adoption isn't Mac OS X or Linux; it's XP. IE8's most significant competition isn't Firefox; it's IE 6 and IE 7.
Admittedly, it's a nice problem most companies would love to have -- "oh no, I can't get people to upgrade to the latest version of my software, because they like using the old version." It's still a problem though since supporting multiple versions of software is not cheap or easy and hampers the adoption of new platforms. After all, you cannot run IE 6 or 7 on Windows 7 so you better make sure people want to run IE 8 or else they won't upgrade.
I think one principal change along with the "nice problem" that XP has demonstrated, is that there is no throwaway society when it comes to software anymore. Windows and Office are relatively stable (and Linux as well) and suit most people’s needs. There was a real tangible reason to upgrade from windows 3.1 (with the 40 floppies) to Windows 95, then 98, NT and Finally XP. There was an exponential increase in operating system development, from Networking in NT to the Internet and broadband.
I just don't see people as prepared to upgrade to a new computer, the way you would from Windows 98 to XP. It is also silly to discuss this among developers who are highly skilled, because practically everyone I know wants me to fix their computer. Installing IE 8 on some peoples machines will actually cause me problems, because they would say "you touched my PC and nothing no longer works on it", so automatic upgrades are for those that find computers easy. At this precise moment in time, a significant amount of people over 30 years old are computationally "semi-literate" and very "software habitual" i.e. they like things as they are, and don't like change. If there is change, it must be gradual, with a lot of support (somehting I have very little time for sadly)
That is the key problem Microsoft has. As an example look at the simply stunning Lawson Mango application. For a typical business, that would involve tens of thousands in training costs - forget the application, just getting staff to a competant level of usage, also factor in new staff. It is that much of a departure from a File-Edit-Tools type application, which is sad, because I'd do anything to work in that type of application environment.
I would say that the .NET framework is now inadvertently tied to the Windows operating system. You can expect C# 4.0 etc. when the next Windows version is released. This is the best way to promote the .NET framework as demonstrated by Vista.littleguru said:
Well... on Windows Vista the upgrade isn't that huge. But it's true that on XP it can be quite a load that gets downloaded.
I would be very surprised if it turned out not to be the case.
A cow has 4 stomachs (if my memory serves me well).Matthew van Eerde said:Does grass have a "grain" -- that is, is it easier to eat grass facing a particular direction?
- When it grazes, the grass goes into the first stomach
- When it sits down (under a tree or in the shade) the second stomach turns the grass in stomach one into little balls and sends it back up to the mouth (regurgitation) for it to be chewed (yummy). That's why cows mouths are usually in motion when they are
- Stomach three then add some stuff that breaks grass down (have you ever tried eating the stuff?)
- Stomach four then acts as a normal stomach does and digests the grass
Random Fact: In a rabbit, what it eats has two phases
- What is eaten has acids etc. first added to break it down, then the food is excreted out.
- The rabbit then eats this and can digest it.
I agree with that, it makes total sense. Only thing is why north-south and not south-north?Dr Herbie said:My gut reastion is that this is probably a side-effect of evolved homing ability (or 'directionality' for want of a better word).
Possibly evolved to make grazing more efficient, so they are less likely to re-graze the same patch immediately?
Makes me want to go and attach a load of magnets to a local herd to see what happens
Was it an evolutionary toss of a coin?
Has weather something to do with it?
What happens to cows on the equator?
Some humans write with the left hand, others prefer the right. I wonder of some cows choose the other way around, just because they are different. I can see it now. A heard of cattle all moo-ing "there's always one isn't there". Maybe I'd better stop now, oh, I've just thought there is the saying "till the cows come home". Maybe cows get annoyed with herdsman forcing them to go back home, when they want to go the other way. I really had better stop now for fear of being termed weird.
I agree with that assessment completely, although they should have just pushed it via automatic updates. The client framework will get people excited over thin air because that is exactly what it is.Maddus Mattus said:vesuvius said:*snip*
The reason they have choosen this setup is because they have more political agenda's running, it's not always about the developers and users needs. They want a large install base for the full-blown .Net framework, so they can compare internet p3nis size with java. As often with these types of decisions, managers have the say.
Install the Java framework, it updates all the time with stuff I dont want. I would catigorize this as another missed oppertunity for Microsoft to be superior
To put it in perspective; what is 100Mb compared with with the size of current updates? not much,....
Quite why they (Microsoft) need ASP.NET and WCF etc. on all their client machines is still a mystery to me? It will never be used. Granted .NET is updated every once in a while, but Java seems every two weeks.The annoying thing with Java, is that it never overwrites or upgrades the previous version. I have seen PC's with 3 or more Java Updates on them. Very messy.