It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am new to Security in Asp.net application. I want to enable SSL in my asp.net local application i have Developed. i need a step by step implementation to ssl to my asp.net project. Most article i found online has only explained the installation of the certificate. As a newbie what is the first thing i will do to convert my http to https. Do I need to change anything in the web.config?
First of all, you have to buy a SSL certificate. That's not free.
Then you need to host in on your local IIS. If you run on Windows, you can activate it in Programs and Features. Then you can install the SSL certificate there (you can find an icon in the IIS manager).
I guess you run the website in Visual Studio, and hosting the website on the IIS is quite different. If you have no experience doing so, I would either recommend starting wih that, or see if you can avoid using the SSL certificate.
Related
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I am going to write a webDAV server hosting in IIS with ASP.NET. I think I have to write a new one because I have to integrate it with our custom security module. Actually I think I have to check some security (membership and roles) concerns on webDAV file request and respond to request based on that security concerns.
How can I write a WebDAV server? Or are there any libraries suitable for me?
Regarding existing libraries - there exists a free webdav project on SourceForge, then there exist paid components on http://webdavsystem.com and we offer WebDAV server within our SecureBlackbox component suite. All of them can be integrated with IIS. Offered level of fine-tuning such as authentication control and filesystem access is of course different. Our SecureBlackbox is biased towards flexibility and feature-richness.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
Actually I am bit of confused right now and need some guidance. I have been offer a project to create web portal to generate report. Scenario is something like this,
Client has a business and he need to check the report of hourly sale. What should I do, should I put the SQL Server online or is there any other way to excess server database remotely. I have no experience in creating web portal, how should I start doing it.
Can anyone guide me in proper manner? I have experience in C#.NET using Visual Studio 2010.
Thanks.
This suggestion is without completely understanding your situation but...
There is an open source package called nopcommerce which has an inventory system, sales and other canned reports and a basic CMS built in.
It also includes all source code in C# and works with SQL Server.
It's generic enough to use for most retail scenarios and going this route will save you TONS of time trying to start from scratch.
I would think you could just download, install and customize and get 95% of everything you need from it.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I have to give my windows form application to other users and We are using shared drive.
I am not sure which is the better option: Giving users "Debug folder" of windows form application or published setup.
There are seveal options available for installing the application on the user's machine, instead of simply allowing them to run it from a network share.
One option is to use ClickOnce to generate a setup file, which can be accessed from a network share.
Compared with giving users access to the debug folder, it allows better control over updating (you can compile and run debug versions as much as you want, then when you're ready, publish it to your users, who will automatically get the latest version). It also allows for giving the users an optimised version of the program, without additional debugging overhead. It also manages installing dependencies, such as the .net framework.
For other advantages see here: http://www.msigeek.com/330/advantages-of-clickonce-deployment
See also: http://msdn.microsoft.com/en-us/library/142dbbz4(v=VS.90).aspx
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
How should I go about making an application with C# and .NET where, say, on one computer a button is pressed that triggers an event on the other?
I saw this:
Recommended way to communicate between processes running on different computers on the same network
I've never heard of WCF, is that what I should try?
You're question is way to broad however I can give you a brief overview of how WCF (and most client/server apps) work.
You create a WCF service and then you reference the WCF service (in VS right click references then add service reference) inside your client application. The click in the client application will send a message to the WCF service that will deal with that message.
As mentioned the getting started guides are pretty decent. The WCF Test Client is a great debugging tool as well. If you open the Visual Studio command prompt and type wcftestclient, it will pop up.
Here are some articles that might be helpful:
http://msdn.microsoft.com/en-us/netframework/aa663324.aspx
http://msdn.microsoft.com/en-us/library/dd936243.aspx
http://msdn.microsoft.com/en-us/library/aa751792.aspx
http://blogs.msdn.com/b/tess/archive/2009/01/09/net-hang-my-application-hangs-after-i-called-my-wcf-service-a-couple-of-times.aspx
http://blogs.msdn.com/b/wenlong/archive/2009/07/26/wcf-4-higher-default-throttling-settings-for-wcf-services.aspx
http://merill.net/2008/10/wcf-performance-optimization-tips/
Yes, I would use WCF, because I know it's pretty easy to get a simple project running with WCF, and that will give you confidence to build on it. (Having said that, I dont have much experience with any other networking technologies.)
Start with this Getting Started tutorial.
Then if you have more specific questions, ask them.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
This'll be my second time doing a CMS and Inventory Management app for my client. This particular client wants it all to be online. Instead of a desktop app, like I did with my previous client. Which is fine I guess, however I'm a little concerned about the security stuff... What if it gets hacked? He basically wants to be able to manage, view, create new and edit existing orders via his website from an "Admin" type interface after he logs in as an Admin, so obviously I'm going to need Roles.
But is this common or normal practice? The website isn't an intranet, or hosted locally, it's remotely hosted.
Yes, its very normal all of my websites have admin interfaces that allow access to just about everything with the proper credentials.
A word of caution however: If you are not sure what you are doing, I'd be very careful about accepting/storing credit cards or other sensitive information(SSN's medical data etc) . Its easy to screw up, and if that stuff get hacked, you may have some serious legal problems to deal with. Consider hiring someone with the right experience to help with security.
Everything you listed is normal to a Web application, whether it's hosted locally or on an intranet, or hosted remotely.
What you need is probably already implemented in other online CMSs (see Orchard CMS), but if you want to roll your own CMS, it's very easy to use ASP.NET MVC; it also has easy integration with Forms Authentication for ASP.NET.