This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
How to encrypt query strings in asp.net?
I am creating one project in asp.net 4.0. I want to encrypt/ decript my url for the security reason/ How can i do this
This is good article for make URL tamper free...
https://web.archive.org/web/20210125142425/https://www.4guysfromrolla.com/articles/083105-1.aspx
Related
This question already has answers here:
Firebase .NET access
(1 answer)
Firebase in c# (API recommendation)
(1 answer)
Closed 5 years ago.
Is is possible to connect ASP.net with firebase database.
If yes please tell me how to do that
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
For our project needs, I created my own ASP.NET Identity 2.0 Provider with SQLite database, and Entity Framework used in MVC 5.2 application. It's methods are all async. All of the problems with the connection to SQLite DB are resolved (I saw many questions regarding this)
So, my question is very simple:
Does it make sense to share my code with the community on GitHub? Can it be really helpful? What do you think?
Thanks for all answers
Not exactly a technical question, but nevertheless: if I found something like this on GitHub I would totally look into it as I have developed similar features and it would definitely help me compare / improve my work.
So, OK. Here is the link on github where you can see and use if you need to my implementation of ASP.NET Identity 2.0 Membership with SQLite database, and Entity Framework OR/M. I'll also add some more info in readme file of repo about how to use/configure etc. your own implementation and how to skip all problems which can take place when you are working with SQLite and Entity Framework
https://github.com/darklektor/ASP.NET-Identity-SQLite-EntityFramework
Thanks for answers guys
Have a good and nice code :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We are converting a major.NET 2.0 project to MVC, we were learning MVC 4 and since MVC 5 is already out, we figured we might as well move straight to MVC 5 since it offers attribute based routing out of the box and .NET 4.5 seems like the platform to develop some chat features we were thinking about using SignalR.
The confusing part for us now is that there are so much information since .NET 2.0 regarding say membership
From research, we saw
Simple Membership
Universal Membership
Identify Membership (1.0, and then 2.x?? what?)
So boils down to one simple question, is ASP.NET Identity THE thing to learn regarding membership when we redesign the app in MVC 5? Simpler Membership / Universal, we can just completely ignore them right?
Sorry all, I'm just really late to the MVC game and I'm trying to catch up. A bit (actually completely) overwhelmed by different articles all talking about different things.
Thanks.
Take a step back and realize what all these "solutions" are doing. They are helping you create an identity in ASP.NET and help manage cookies on the client. When you think about it that way you will realize that you need very little to build a good authentication scheme. I always leverage what is in ASP.NET in regards to principal and cookie management, but ignore the database stuff and just implement it myself.
I wrote this post that I hope will help you. You will realize there really isn't much too authentication.
http://www.khalidabuhakmeh.com/asp-net-mvc-5-authentication-breakdown-part-deux
This article was recently listed on the asp.net community site. :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
actually I'm planning on doing a little bigger project. I want to make an Android-App, iOS-App and a ASP.NET web-page, and all three should use the same DataBase (preferable MS SQL Server).
Is JSON the best choice? When yes, how do I have to build up the whole thing?
Can I write only one service and every plattform then can read and send to this service?
What kind of service should that be, so I can look further what I have to learn?
If you're using SQL Server, I assume you are using C# or VB.NET.
You can write a single service with Web API and it can output both XML and JSON. You can configure the default output format to be one or the other - for example, you can configure the API to by default emit JSON objects, but if the person requesting data specifies an HTTP header, you can emit XML instead.
But currently JSON is the standard for web services, so I would go with JSON and build around that.
You can make a ASMX service or WCF service and you can use these service in web using javascript or by codebehind For Android and ios you can call webservice by requesting in json format actually one asmx service can response XML as well as JSON format
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
We are converting legacy VB application to ASP.Net application.
We have the several word documents stored in SQL server database.
Users should be able to edit the word documents and store it in the database.
I am trying to use iFrame whose source would be the word document in the server.
Users will have MS word installed on client PC but not on the server.
But how can i get the changed file in ASP.Net and store it back on the server.
Please advise me.
Regards,
Mugil.
If you want to edit documents in MS Word and store them online, you probably have to write a plugin for Word. A simple and crude solution would be to require the users to save the document locally and then upload it via your website.
You probably want to take a look at Sharepoint.