multi-clients web application,should I use custom user controls or a common user control
Say my company is going to build a complicated asp.net web form education system. One of the module is web based registration. To make it flexiable, we decide to use user control(ascx) with rule-engine (work flow) regulating all business logic behide them. Thus in future,for different clients, we can simply config basic existing rules or adding new rules.(Rules stored in db or XML per client).
Sharing authentication methods across API and web app
I’m wanting to share an authentication implementation across a web application, and web API. The web application will be ASP.NET (mostly MVC 4), the API will be mostly ASP.NET WEB API, though I anticipate it will also have a few custom modules or handlers.
SOA in .NET 4.5 with MSMQ Durability
I have been doing some investigation regarding ASP.NET Web API. I have enjoyed using the WCF REST template to create new RESTful web services, and Web API seems to be a cleaner iteration on that.
Licensing approach for .NET library that might be used desktop / web-service / cloud environment
I am looking for advice how to architect licensing for a .NET library. I am not asking for tool/service recommendations or something like that.
Should I implement BackBone.js into my ASP.NET WebForms applications?
Our application is using the WinForms Framework.
add a prefix to localhost [closed]
Closed 11 years ago.
Setting up ASP.NET structure for code [closed]
Closed 9 years ago.
Organizing ASP.Net Single Page Application with Nancy
As a personal project, I’m creating a single page, asp.net web application using Nancy to provide RESTful services to the single page. Due to the complexity of the single page, particularly the JavaScripts used, I’ve think creating a dedicated project for the client side of web development and another for service side will organize and simplify the development.
How to create a Request Specific Thread Safe Static int Counter?
In one of my server application I have a class that look like,
Idea to develop a caching server between IIS and SQL Server
I work on a few high traffic websites that all share the same database and that are all heavily database driven. Our SQL server is max-ed out and, although we have already implemented many changes that have helped but the server is still working too hard.