Featured post

c# - Usage of Server Side Controls in MVC Frame work -

i using asp.net 4.0 , mvc 2.0 web application. project requiremrnt have use server side control in application not possibl in noraml case. ideally want use adrotator control , datalist control. i saw few samples , references in codepleax mvc controllib howwver found less useful. can tell how utilize theese controls in asp.net application along mvc. note: please provide functionalities related adrotator , datalist controls not equivalent functionalities thanks in advace. mvc pages not use normal .net solution makes use of normal .net components impossible. a normal .net page use event driven solution call different methods service side mvc use actions , view completly different way handle things. also, mvc not use viewstate normal .net controlls require. found article discussing mixing of normal .net , mvc.

asp.net - How to invoke a Forms Auth login modal dialog instead of redirecting to a loginUrl signin page? -


i've finished implementing modal dialog login popup asp.net website. experience similar digg.com. when log in, fancy popup modal dialog (provided jquery tools overlay control). dialog ascx file in master page, it's available globally. uses pagemethod validate current user. if validation succeeds, call window.location.reload(); in pagemethod's success callback.

this works great when logging in on page doesn't require authentication, when non-auth users trying navigate page requires auth?

is possible modify web.config file instead of redirecting signin.aspx page non-authenticated users invoke modal dialog instead?

let's non-authenticated user on default.aspx doesn't require auth. wants navigate "add.aspx" does require auth. what's best way handle modal dialog popup?

if have use dedicated page, guess i'll have signin.aspx page invokes dialog when loads , if authentication succeeds, it'll use javascript redirect destination page.

but ideally, i'd login default.page , redirect "add.aspx" script.

since didn't feedback , went ahead , "solved" issue conventionally. still have dedicated login.aspx page it's used in cases users navigate directly page requiring authentication.

in case, let asp.net redirect login.aspx, , using client script invoke popup dialog. normal authentication using webmethod , redirect needed. if user cancels dialog, redirect default.aspx.

seems there's no getting around need dedicated login page.


Comments

Popular posts from this blog

c# - Usage of Server Side Controls in MVC Frame work -

cocoa - Nesting arrays into NSDictionary object (Objective-C) -

ios - Very simple iPhone App crashes on UILabel settext -