Access Session variable of ASP.Net solution into MVC project inside same solution

Question

0.00/5 (No votes)

See more:

Hi,
I have an old website created in VS 2008 i have migrate it into new framework VS 2012.
Now i have a new request to create a module in MVC but inside same solution. I have created a new MVC project inside same solution but i have following issues -

My default login into website is available in my traditional website (old) and i need to access the Session variable into my newly created project which is in MVC.

So how can i achieve it to navigate to MVC website and access same Session variable inside it.

Posted 4-Sep-15 4:07am

Ajay_Saini

Add a Solution

Comments

F-ES Sitecore 4-Sep-15 10:17am

Just convert the entire site to MVC if that's what you want, you can't easily share session between sites. Doing a half-and-half is doomed to failure, and it also shows that people are probably making bad decisions when it comes to the solution architecture.

Your best bet is probably to encrypt the data you want to send and add it to the url as a parameter, then your new site and decrypt it.

Ajay_Saini 7-Sep-15 10:48am

My old application is using PageMethods of ScriptManager and there is no server side controls are used in any of the pages all the controls are normal HTML controls. So it is not feasible for us to convert into MVC. We need to add a separate project (in MVC) that's why i am keen to know about the above query.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)