Seperate .Net 2.0 Threads from 1.1

[Diesel]

It's really annoying when you realize someone is talking about .net 2.0 and doesn't realize a feature exists and your advising them on how to re-create that feature in 1.1.

At least I find it annoying.

Can we add a new topic tree for the 2.0 threads?

 

[snarfblam]

I don't know if it is a good idea to double the forums. Perhaps 2.0 users will just kinda forget that the 1.1 topics are there and people won't get advice they otherwise would. I agree that this is an issue that should be addressed somehow, though. As far as someone not being aware that a feature is present in 2.0, that's someone not doing simple research (google, object browser) before they post. For the time being, perhaps the best approach would be to check someone's profile to see which version and which language they are using.

 

[Diesel]

What if in their profile they list multiple versions and multiple languages?

Besides, you shouldn't have to check a profile everytime you answer a question.

 

[snarfblam]

What if in their profile they list multiple versions and multiple languages?

Besides, you shouldn't have to check a profile everytime you answer a question.

You mean what if they are like me? I would assume that they are using the most current version, and I would provide code examples in the language most comfortable to me that we have in common. Even without the confusion of which version a user has, how have you determined which language to use in the past? Sometimes I gave code samples in both VB and C#, and sometimes I said "here is some vb, if you use C# im sure you can manage the translation" or vice-versa. I personally won't hesitate to say "use so-and-so class, but if you are using version 1.1 you are out of luck." Of course, I am not aware of every single difference between versions and the time will surely come when I don't make a point of which versions a feature is available in or I tell a user of a particular version to use something that isn't available to them, but I doubt it will be common place.

No, you shouldn't have to check a profile each time you post, but I was only recommending doing so as a temporary solution.

I don't know if it is possible with VBulletin, but it would be nice if we had some simple icons that we could put next to our names or below our avatars that indicated what language(s) we used primarily. To me that would be an ideal solution.

 

[Cags]

I must admit I've seen quite a few cases of people recommending functionality that I've not got access to (thankfully this has never happened when I've asked questions, only when viewing other posts). This can sometimes cause problems as people (especially those new to programming) can get easily confused. TryParse is the only example I can come up with off the top of my head. With this being said I would have to agree with marble_eater in saying that there isn't much that can easily be done about it. It would require an entirely seperate forum which duplicates the exact same topics.

I think the thing that would help the most is people actually filling in their profiles correctly (often I post suggestions in c#, when people want VB but haven't specified that in their profile). Also perhaps when people are posting suggestions that revolve around 2.0 they can inform everyone reading the thread that the feature is 2.0 only (assuming they know).

 

[Diesel]

With this being said I would have to agree with marble_eater in saying that there isn't much that can easily be done about it. It would require an entirely seperate forum which duplicates the exact same topics.

That's what Im asking for. How hard is that?


Also, don't take this the wrong way Marble but...you need to get laid.
I can't believe you actually spent time making that pic with the language bars on it.

 

[mskeel]

Also, don't take this the wrong way Marble but...you need to get laid.
I can't believe you actually spent time making that pic with the language bars on it.

HA HA HAH !H!!!H HAHA !!

 

[mskeel]

For the record, I think the language bar idea is a good one. I don't know how feasible it is, but it is a good idea.

Similiarly annoying is how the ExtremeVB forum has strated a section for VB.Net in the past year or so when they used to be strictly VB6 oriented. That has effectively created two seperate forums under the same roof that are relatively close together. I was once again reprimanded by members of the EVB forum about posting the same thread here and there. I thought they were different forums and it was confusing. Since the comunities are so close, why not bring the VB.net sections of EVB forum under the extreme .Net?

 

[snarfblam]

Also, don't take this the wrong way Marble but...you need to get laid.
I can't believe you actually spent time making that pic with the language bars on it.

And just how long do you think it took me to draw three rectangles, some text and copy two images? Besides, I only program for sh**s and giggles, so why not draw some silly pictures for the programming forum for the same silly reason.

Similiarly annoying is how the ExtremeVB forum has strated a section for VB.Net in the past year or so when they used to be strictly VB6 oriented. That has effectively created two seperate forums under the same roof that are relatively close together.

That was my initial sentiment exactly. You know what, though? The average maturity level of the people at the ExtremeVB forum is a magnitude of order lower than here. I might get a little edgy or even approach childish on occasion, but I gave up on ExtremeVB because it does nothing but give me a headache. To me the two forums are more than just a separation of languages.

 

[Nerseus]

I doubt we'll create a separate language-version forum. There's already enough "confusion" about which forum to use. Adding more will just mean looking in more forums for help.

I think of the different languages similar to different Database questions. There's one DB forum, not one for SQL Server, Access, DB, Oracle, etc. A question like "How do I select names that start with Bob?" have different answers depending on the DB being used.

Even worse - someone asks "How do I pass a value from one form to another?" and you answer with a C# snippet and they're mad because they use VB.NET (or vice versa). In my opinion, tough noogies!

I think the trial and error system works best. Meaning, let users ask questions however they want. If they want an answer for C# 2.0, they should mention it. In time - maybe six months give or take - it will be assumed that questions are about .NET 2.0 and you'll have to mention if you only have .NET 1.1.

Advanced users will post the right question the first time: "How would I iterate over a typed ArrayList in C# 2.0?". The other users will just have to wait for TWO replies until they learn.
"How do I loop over an ArrayList"
"Here's how (gives example using C# 2.0 features)"
"Sorry, I'm using C# 1.1 and we don't have generics"
"Oh, here you go (gives other example)"

I liken the art of posting a question to the art of searching with a search engine. You'll get better the more you practice.

-ner

 

[Nate Bross]

Marble, I like the idea of the icons under our names saying what language and version we are using.

Additionally I agree with Nerseus that in time .NET 2.0 will be assumed, and 90% of the confusion will subside.