View Complete Post
Hello, I am working in a aspx web application that must be built in several separate "modules" with different functionality which will be partly developed by different teams.
However, I need the completed app to reside in ONE virtual directory. There will be a single startup page. I need session state to be preserved across pages in different modules.
I structured it as one solution with different Web Projects and one class library project with common functionalities.
Questions:
1) is this the right approach to do this? Or which one would be better?
2) each time I add a new web project to the solution, a new web.config gets created. What do I do and where do I put them?
VS 2010 + framework 4.0 + TFS
Regarding TFS and source control, I have a single Team project, the solution and web projects are inside it.
Thanks!
Alsalamo 3alaykom ,
as we know that if you use Intelligencia.UrlRewriter.RewriterHttpModule or IIS URL Rewriting , we will face problems with arabic urls
as this
http://localhost:1234/Pages/???? ?????? ?????? ??????????
and the Rule is :
<rewrite url="~/Pages/(.+)" to="~/ShowPages.aspx?Page=$1" />
you will recive the QueryString["Page"] Like this
Ãâ¢Ã¢â¬Â ÃËçÃËæÃËè ÃËçÃâ¢Ã¢â¬Å¾ÃËùÃâ¢Ã¢â¬Â¦Ãâ¢Ã  ÃËï Ãâ¢Ã¢â¬Å¾Ãâ¢Ã¢â¬Å¾ÃËôÃËäÃâ¢Ãâ Ãâ¢Ã¢â¬Â ÃËçÃâ¢Ã¢â¬Å¾ÃËãÃâ¢ÃâÃËçÃËïÃâ¢Ã  Ãâ¢Ã¢â¬Â¦Ãâ¢Ã  ÃËé
so it's a big problem , and there is a solution that is :
remove the Rule of that rewriting ,,
then open your Global.asax file and Application_BeginRequest method exactly
use the following code to handle you request
void Application_BeginRequest(object sender, EventArgs e) { if (HttpContext.Current.Request.Url.ToString().Contains("/Pages/")) { String[] txt= Regex.Split(HttpContext.Current.Request.Url.ToString(), @"/"); String page = txt[txt.Length-1]; HttpContext.Current.RewritePath("~/Sh
This article explains how you can use Active Directory Federation Services (AD FS) 2.0 to claims-enable Windows Communication Foundation (WCF) services and browser-based applications. The focus is on the token issuance functionality in AD FS 2.0. You'll find out how to use AD FS 2.0 as an identity provider; set up an AD FS 2.0 security token service (STS) to interact with WCF; federate AD FS 2.0 with your custom STS or another AD FS 2.0; enable Web single sign-on and federation with WS-Federation and SAML 2.0 protocols; and externalize authentication logic through Visual Studio. You'll come away appreciating how AD FS 2.0 and Windows Identity Foundation make programming identity solutions in Windows less of a chore.
Zulfiqar Ahmed
MSDN Magazine November 2009
We introduce you to the EDI functionality within BizTalk Server 2006 R2, illustrating schema creation, document mapping, EDI delivery and transmission, and exception handling.
Mark Beckner
MSDN Magazine August 2008
One-time passwords offer solutions to dictionary attacks, phishing, interception, and lots of other security breaches. Here's how it all works.
Dan Griffin
MSDN Magazine May 2008
OBA solution patterns help architects and developers build Office Business Applications (OBAs). This article introduces the seven core OBA solution patterns and applies one to a real-world problem.
Steve Fox
MSDN Magazine March 2008
WSS 3.0 introduces a new deployment mechanism that lets you move your development efforts into a staging or production environment.
Ted Pattison
MSDN Magazine August 2007
State management in Web applications is a contentious issue. Should you store user data per session or should you persist it across sessions? You can easily store information temporarily while someone navigates your site by using session state.
Fritz Onion
MSDN Magazine April 2006
Hall of Fame Twitter Terms of Service Privacy Policy Contact Us Archives Tell A Friend