What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 130 Stack Exchange communities.

I'm not really sure being an ASP.NET developer, but do non ASP.NET developers (or ASP.NET developers working on other things) use the tag when not talking about ASP.NET web forms? e.g. do PHP developers call their web application pages (or pages with forms) WebForms?

I only ask as when posting a question relating to them I was given the option of or

It would seem sensible to make those questions all tagged ...but if the tag is ambiguous, that is a big manual effort as there were >900 tagged ...

share|improve this question

closed as off-topic by Martijn Pieters, rene, ProgramFOX, Shadow Wizard, Emrakul Jul 11 at 23:26

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Martijn Pieters, rene, ProgramFOX, Shadow Wizard, Emrakul
If this question can be reworded to fit the rules in the help center, please edit the question.

5 Answers 5

up vote 4 down vote accepted
+100

After spending a bit of time looking into this, I believe it is pointless to try to make ASP.NET-pure.

The vast majority of the ASP.NET-specific questions in webforms already have a qualifying tag of some sort (the link is to questions that aren't clearly ASP.NET). So they're not a problem.

The vast majority of the ASP.NET-specific questions in asp.net-webforms also already have some manner of qualifying tag.

So merging and synonymizing into [webforms] would simplify the situation greatly without introducing very much ambiguity (just over 100 questions would benefit from being retagged manually first, adding ).

It would also keep the naming consistent: and for ASP.NET view engines.

Note that we should not be looking for consistency with and , as those are actually complete product names (and as BoltClock mentioned, have issues of their own).

Those looking to distinguish ASP.NET's webforms from, say, Drupal's can simply combine tags to produce the desired results.

share|improve this answer
    
Just finished re-tagging a question and had this very same question. Seems worth re-visiting now that we have better tag merging tools available to us and there are around 4k questions in either tag... –  AnonJr Sep 26 '13 at 14:08
    
Thanks for the ping, @AnonJr - didn't realize these had been synonymized for over a year but never merged! That's done now. –  Shog9 Sep 26 '13 at 17:17
    
Not a problem. :) –  AnonJr Sep 26 '13 at 17:29

and should be merged.

on the other hand should be kept separate, since there are other frameworks building on ASP.NET, that are not WebForms.

share|improve this answer

I'll agree that most people, when hearing ASP.NET, think of webforms.

Suggest that the tag is a broader set of technologies beneath webforms. There are many technologies or project types extending ASP.NET:

  • MVC
  • ​WCF
  • webforms
  • dynamic data
  • SOAP web services

ASP.NET is a web application framework. All questions the project types on top deserve their own tag as well.

share|improve this answer
1  
WCF does not extend ASP.NET. "SOAP Web Services" extend a very tiny part of ASP.NET, but are now considered to be "legacy technology" by Microsoft, so I wouldn't spend much effort thinking about them. In fact, ASP.NET is a superset, containing web forms, MVC and dynamic data (not WCF). –  John Saunders Aug 16 '10 at 4:38

I'm not really sure being an ASP.NET developer, but do non ASP.NET developers (or ASP.NET developers working on other things) use the tag when not talking about ASP.NET web forms? e.g. do PHP developers call their web application pages (or pages with forms) WebForms?

We don't have a special name for PHP-powered pages/scripts. We just say that we write them in PHP. Neither is PHP itself a framework; it is a language. There do exist major PHP frameworks, but none called WebForms as far as I know.

It would seem sensible to make those questions all tagged ...but if the tag is ambiguous, that is a big manual effort as there were >900 tagged ...

This is what really bothers me. By now, there's currently quite a divide in the tag between questions about ASP.NET WebForms and questions about generic "Web forms" used to refer to, well, forms on the Web, regardless of server technology (or even pure frontend ). The winner, by some margin, is , covering almost 1800 questions, with the other 1200-ish being unrelated to ASP.NET.

I'm inclined to go with what CodeInChaos has proposed, as itself is the framework used for developing Web apps on the Microsoft stack, and based on that are different sub-frameworks such as ASP.NET WebForms, ASP.NET MVC, etc.

Of course, ASP.NET MVC has its own taxonomy quandary, but that one is rather unfortunate as "MVC" is a well-known pattern that is almost entirely language and platform agnostic. "Web forms", I feel however, is a different beast...

share|improve this answer
    
Disclaimer: I honestly, truly have no idea what I'm talking about. –  BoltClock's a Unicorn May 11 '12 at 17:22
    
reputation and experience count for nothing ;) –  davidsleeps May 13 '12 at 22:44

Bump. I do support the idea of merge.

clearly states that it's related to ASP.NET:

Web Forms is a part of the ASP.NET web application framework. It is one of the different programming models you can use to create ASP.NET web applications.

Tagging by it anything not related to is tag misuse and is not excuse do not merge.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged .