I have multiple web application in a single solution. It's not possible to use sessions to transfer data between pages of these applications. How can I do this in a secure manner?
Thanks.
Thanks for answers.
After more research I found Single sing on (SSO) to solve the problem.
Read the article about "Architectural approach of a domain independent Single Sign On implementation for ASP.NET applications." here:
http://www.codeproject.com/Articles/106439/Single-Sign-On-SSO-for-cross-domain-ASP-NET-applic
http://www.codeproject.com/Articles/429166/Basics-of-Single-Sign-on-SSO
Related
We need to share data between subdomains in web sites using different applications developed using ASP.Net and deployed on IIS. We have following ideas in mind :-
a. Sharing data using cookies : But this idea will allow only to share us simple strings and more over it will get failed if browser don't support cookies
b. Sharing data using session : But for that we will have to use out proc session handlining techniques
Can any one please let us know if there is some other good technique for this?
Thanks
Tarunjit Singh
To share data, use a database, or use common files, and use that files to save there yous common data.
Other possible solutions.
If you like to send data from one page to another, you can use post them.
You can also use the url, to send data on variables.
You can also use memory mapped files.
And here is one more example how to share memory across different apps
Dumb question (maybe) I have searched online but I'm looking for somewhat a yes no type of answer. If you ever see a website with just xxx.com/xxx.aspx ... was that application created using Web Forms? Is ASPX only associated with Web Forms?
Thanks
To answer your question in yes or no (as asked), NO.
You can do that in ASP.NET MVC as well, by setting up the routing in that fashion. But I don't think anybody would do that.
On another note, if you have come across a website which is xxx.com/xxx.aspx, you can make a decently good bet that it was developed in ASP.NET WebForms.
Hope that helps!!!
Technically no. The web server software determines how to handle every request. It could be configured pretty easily to say that any requests for a file with a .aspx extension should be handled by the PHP parser, or Ruby, or whatever. Or, if using ASP.NET MVC, you could set up routes that resources that end in .aspx are still handled as MVC pages.
Of course, there aren't many reasons that someone would WANT to do that. The only reason I can think to do so would be if you're explicitly trying to make people think that a page is using a different technology than it is. And I don't see that being a common goal.
I would like to know what are the basic steps involved in setting up your application to able to read data from another application. Then take that data and modify it and send it back to the application.
The data being read will have over 100 fields.... what is the most efficent way to store them? Put them in a class object?
I know web services are involved...any other info would be great!
The application is in .NET using vb
Thanks
You may need to be more specific about your requirements to get a truly useful answer. That said, Windows Communication Foundation (WCF) is likely to make your life much easier. Google for tutorials -- I can't say I have a favorite. You can handle one- or two-way communication readily with WCF, and you can then focus more on making your application logic work.
Is there anyone knows about list of web servers which is used in embedded system ??. I have used hiawatha, is there any others ?.
Boa was the first one I came to think of. Wikipedia has a fairly comprehensive Comparison of lightweight web servers.
I am struggling to make a decision regarding the correct organisation for a web service. Should I have multiple ASMX's representing the different functionality in the web service, or should I have a single ASMX?
If I have multiple ASMX's, does this not constitute multiple web services?
If I have a single ASMX, how do I organise my code (currently my ASMX represents a single class)?
Thanks for any advise!
Ben
I would recommend multiple .asmx's mapping to different functional aspects of your app, otherwise you're going to end up with a whopper of an end point. Far too often I see a single endpoint with about 50 web service methods, it's nasty on the end user's dev to have to work with that.
Kev
A way solve the problem of multiple asmx described in the original question.
Read this http://www.freddes.se/2009/02/16/multiple-web-service-references-sharing-types/
and get to know wsdl.exe it is your friend when using .net2 webservices.