Help me organize my posts about using jQuery with ASP.NET
ASP.NET, General, jQuery By Dave Ward. Posted November 29, 2011
One of the longest running themes here has been the compelling intersection between ASP.NET and jQuery. Beginning with my post about using jQuery to circumvent ASP.NET AJAX’s client-side apparatus for calling ASMX services, I’ve been writing about using ASP.NET and jQuery since the Spring of 2008.
As these related posts have accumulated over the years, I’ve made an effort to weave a thread of cross-links between them posts where appropriate. However, it’s nearly impossible to anticipate every possible entry point and subsequent path that someone might find themselves following here.
So, I’ve decided to finally do what I should have done a year or two ago: Create a top-level index to organize and improve the accessibility of my content for ASP.NET developers interested in integrating jQuery into their sites.
You can see my first draft of that here: jQuery for the ASP.NET Developer
Unlike the other content here, I’m publishing this one long before it’s “finished”. My hope is that I can solicit early feedback to help better construct a useful narrative while the document is still in its formative stages. So, if you have any feedback on the current page or what you think should ultimately be there, please leave me a comment on either this post or that page, contact me directly, or even @mention it my way on Twitter.
Similar posts
What do you think?
I appreciate all of your comments, but please try to stay on topic. If you have a question unrelated to this post, I recommend posting on the ASP.NET forums or Stack Overflow instead.
If you're replying to another comment, use the threading feature by clicking "Reply to this comment" before submitting your own.
Hi Dave,
I think that your decision to create the top-level index page will be super effective :).
Now, one thing bothers me though – if I’m looking from the perspective of a .NET guy, I might be looking for a narrow context and I would only seek answers in that context. Having this in mind, I would be so bold as to split this into several categories:
ASP.NET (WebForms)
ASP.NET MVC
ASMX (WebServices)
WCF Web Services
Depending on the project, the developer might be tied onto only one of these so they would look for solutions only in one of those contexts.
I know that some advises and practices apply across several (or sometimes all) of these, but still I’d like to be able to view solutions in a narrow context in order to ease my mind that there’s something I can do without having to switch context (for example from WebForms to MVC).
I would in fact like to see all of these mentioned in one place however, because I’m not a fan of narrow context :) and I would like to be aware of what alternatives are there for me.
Hope my two cents help you out.
Cheers!