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
I was wondering what is the preferred method of licensing a web site?
I distribute precomplied versions of my web sites with editable APSX files, the code behind is complied into separate DLL's for each page.
I have thought of implementing some sort of text injection into each page, similar to what Telerik controls do, when using a trial version. This demo text would disappear if using a licensed version.
One way I would think is to have the web site contact a web service to determine the license status but this would be an issue if the web service is down for any reason.
Thanks
It's absolutely unacceptable to have your controls rely on an external web service to check the license. The only thing you're going to get out of that is pissed off customers and maintenance issues for yourself.
I strongly encourage you to go with the honor system, or a very simple licensing key file (that never expires). You're selling a web site, not video games. Unless you know for a fact that you are losing significant money because of piracy of your product, do not waste your time. Remember the first rule of optimization!
you could build some sort of license controlmechanism into your website. therefore you could use the URL of the site (typically you sell your asp.net app for one or two urls to somebody), and e.g. you could also build some hardware-key-references into your license mechanism, so that a copy of your software is not possible to run on a different machine.
but keep in mind, all restrictions you build in will result in more work for your paying clients, and there is always somebody who want to try to use your software without paying it!
Related
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 2 years ago.
Improve this question
I'm making an app with a friend. I have a server which supports PHP and MySQL which my app is based on.
So we need to collaborate when making the app.
We are using Dreamweaver and NetBeans and apps on our phones...
The question is:
Is it secure to put the app we are developing on the web while its under development, and what should we use to protect it from the outside world?
Will Password Protected FTP be a good solution? or HTTP with a password protected folder?
I have seen there is a problem in HTTP protected folders. The login accepts a some other passwords too. Like if the password is helloworld123 and you login with helloworld it would accept and login?
SO I think HTTP will not be a good solution. And if it is then how should i make it more secure?
So what should I use? FTP or HTTP? thanks...
If you are developing an application, you should really be developing it locally.
You will rapidly tire of testing a change by uploading it to a remote server.
Additionally, what happens if your friend makes a change, how do you know that he has made that change? You will very quickly get collisions in code which totally ruin your collaboration.
So first of all, you should both install a LAMP/MAMP/WAMP stack locally. You should be testing everything locally, and you don't need to publish it to a server to test.
Then, you should be using some kind of version control in order to add any changes you make to a remote repository. This means that then you and your friend can work in isolation from each other, and then commit your own changes to a repository, and then you can merge the branches as you go.
When your application is then finished, you can then start to think about putting it into a production ready state by adding it to a server.
Sign up for an account at GitHub.com read as much as you can about how version control works, because if you intend to work together on anything you need to wrap your head around it.
If possible I'd always reccomend using localhost and syncing with Dropbox or any similar app. Otherwise you can try .htaccess to prevent anyone other than you and your friend from accessing your page.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I am tired of having to manage projects manually. We use subversion for version control, but ultimately, I want an app that can:
Send out notifications to clients on the progress of their projects
Allow clients to log in and see screenshots of projects
Keep track of money paid, as well as invoice due dates and how much is outstanding
Allow clients to post any queries regarding the project in an area
Manage several projects
I currently use
SubVersion
WHMCS --> would be great if it could integrate into this
Any suggestions would be great? Or might I have to write an app like this myself?
Redmine
Redmine is a flexible project
management web application. Written
using Ruby on Rails framework, it is
cross-platform and cross-database.
Redmine is open source and released
under the terms of the GNU General
Public License v2 (GPL). Features
Below are some of the main features of
Redmine.
Multiple projects support
Flexible role based access control
Flexible issue tracking system
Gantt chart and calendar
News, documents & files management
Feeds & email notifications
Per project wiki
Per project forums
Time tracking
Custom fields for issues, time-entries, projects and users
SCM integration (SVN, CVS, Git, Mercurial, Bazaar and Darcs)
Issue creation via email
Multiple LDAP authentication support
User self-registration support
Multilanguage support
Multiple databases support
Go Redmine site
You should definately check out Gemini. This has loads of awesome features and can do all of the above (plus a whole lot more). Also, we'll be bringing out some great new functionality on the finance side in the next few weeks.
Dave
I've been looking at Redmine: http://www.redmine.org/
As of now, I've only been looking at it for my 2 person company, and as it integrages subversion and other version control system directly into projects, I think it's an OK choise.
But as mentioned, I haven't used it in production like environemts yet, but it look well tested.
There is also a Turnkey version of it, which is ready to be used as a live CD or in a Virtual Machine: http://www.turnkeylinux.org/redmine
/Kristoffer
If you are looking for something that is hosted I would consider assembla.com. It has just about every feature you could want, and has worked really well for me in the past.
http://www.assembla.com/
We use PivotalTracker
Doesn't have all the features you mention, but it is useful for client interaction and project management.
You could write the app yourself, but you'd likely be better off just going with a SaaS! Believe it.
Your software needs are a bit ahead of what traditional project management apps offer, and it is likely you'll find many systems to be insufficient.
Warning: Just because most PM apps will be insufficient doesn't mean you should settle with multiple different apps. This will lead to double entry, inefficiency, and a list of other problems that come with apps that don't integrate properly. You're better off with something that combines everything you need into one system.
You could try WORKetc, they have a 14 day free trial and combine all the core essentials for web devs. CRM, Project management, collaboration tools, billing, support tools, email marketing, and even client logins (invite clients/contractors to check on projects you're working on related to them + they can collaborate).
WORKetc combines key tools so that it can be used to manage an entire small business. Combined alerts, reminders, calendars, to-dos, document sharing, and a bunch of other features. Worth looking into, other than that I'd recommend looking at the Google Apps Marketplace. Cheers!
It all depends on the size and scope of your projects.
I would say that JIRA is the best system available at the moment and if you only require a small number of users (<=10) then it is only $10 a month.
It's definitely the most complete system out there but obviously there is the hurdle of cost and getting it set up (there is a lot of initial set up to get workflows and things working how you like them).
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
what are different ways that we can do some optimum level of stress testing for asp.net application before moving it to the production environment ?
Here is the free tool for the stress testing in asp.net application.
https://learn.microsoft.com/en-us/archive/blogs/alikl/stress-test-asp-net-web-application-with-free-wcat-tool
Another is called asp.net performance engineering which will tell how we can stress application.
https://learn.microsoft.com/en-us/archive/blogs/alikl/asp-net-performance-engineering-stress-test-your-architecture-design-and-code
Also go through the following post:
Best way to stress test a website
From my experience before moving to the production environment please take of following things.
set debug=false into the web.config
set trace enabled=false into the web.config
Always use precompiled version of your code.
Compile your project into the release mode.
Publish your code if you are using asp.net 2.0 or higher version
User caching api as much as possible.
Decrease your html kb.
remove blank spaces from the asp.net html code.
Use stylesheet as external .css file
USE IIS Compression if poosible.
Put your javascript file in .js files
Use Server.Transfer instead of Response.redirect
Use Inproc Session State if possible.
Use Viewstate efficiently- Use controlstate instead of viewstate which is newer feature in asp.net 2.0
Avoid giving big name to controls it will increase your html kb.
Use Div instead of tables it will decrease your size.
Do IIS Performance tuning as per your requirement
Here is the good link that teaches us good way of deployment in production environment.
http://www.vbdotnetheaven.com/UploadFile/dsdaf/111222006014732AM/1.aspx
Apache JMeter (http://jmeter.apache.org/) is an excellent tool for stress-testing web applications. It can be used with any web server, not just Apache.
Visual Studio 2010 provides some fantastic Test Automation tools and also for Load Testing the web applications.
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 2 years ago.
Improve this question
I have a customer who is being dogged pretty hard by SOX auditors regarding the deployment practices of our ASP.NET applications. Care is taken to be sure to use appropriate file- and folder-level security and authorization. Only those few with deployment privileges can copy an up to the product server (typically done using secure FTP).
However, the file/folder-level security and the requirement of secure FTP isn't enough for the bean counters. They want system logs of who deployed what when, what version replaced what version (and why), and generally lots of other minutiae designed to keep the business from being Office Spaced (the bean counters apparently want the rounded cents all to themselves).
What are your suggestions for making the auditors happy? We don't mind throwing some dollars at this (in fact, I think we would probably throw big dollars at a good enough solution).
You probably want to look at an automated deployment solution and you are going to need a formal change control process. We use anthill pro. It can track what version and when it was deployed.
To satify sox we had a weekly meeting of what was getting deployed when. It had to be approved by compliance manager and each deployment needed to have a form filled out explaining what, why and how something was being changed. Once the form was filled out a third person had to be involved (not the person requesting or approving, neither of them can have access to the production environment, because of the seperation of duties rule you have to follow) to make the change and the change was based off of what was in the "change document" no outside communication from the person making the request. Once deployed, all people had to sign off that it was done and when.
It shouldn't be too hard to meet the requirements, it might require some changes to your development processes but it's definately possible.
What you need is:
A task tracking system, showing descriptions of work, and approvals
The ability to link documents, as well as packages to this system.
A test system to test your deployments onto.
Finally all deployments must be done via installation packages, and other scripted means.
Any manual changes must be documented and approved too.
Also turn on auditing, run regular security tests, and document almost everything.
All of this is possible with a number of systems, the biggest change is the changes to your internal processes.
You might want to take a look at the auditing features provided by NTFS.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
We are designing a survey application with the following features
The users will be able to select questions from a set of predefined questions.
Each question has a question type defined which dictates the type of answer (multiple choice, DB look up, free text etc)
The user can create a hierarchy of sections with multiple questions with in each section.
The responses of the survey will be stored to an SQL server database.
There is also a requirement to generate an output document from each survey response.
We are planning to implement this application using ASP.net.
I am looking for suggestions which will help us reduce the development effort. Is there any commercial/open source application which we can customize for our needs? is there any ready-made components which helps creation of dynamic ASP.net pages? I am only interested in application which i can host locally, as this has to be integrated to an existing application.
This may not be an exact fit, but worth looking at: Surveymonkey.
Unless feedback systems are your business's core competency, you'd be best off using a third-party system. Building a survey system is not as easy as it might seem, especially when it comes to reporting. Sure, you'll be able to bang out some simple reports without too much trouble, but every change wanted by a customer (or your boss) is time you'll be dumping into your survey and reporting engine when it could be spent on your actual business. Do yourself a favor and outsource that headache to a third party.
If your needs are simple, a freebie site like SurveyMonkey would be just fine. If you're looking for something more sophisticated, such as support for phone surveys, more advanced reporting, etc., you'd need to pay for a more advanced service, such as (cough) the one I work for.
http://www.codeplex.com/WebSurvey
looks like a good place to start
Try Zodiac.NET Survey Engine. It can be integrated direct in your ASP.NET website. No much work needed.
NSurvey used to exist for this, but I think they've gone solely commercial. If you can dig up the last open source release, it might be a good starting point.
Otherwise, don't build it. Subscribe to Wufoo
Another option would be to have users use InfoPath or Adobe Designer to create the survey forms that are distributed to survey takers (either by e-mail or web-site).
With InfoPath, you can have the responses call back to Web Services that you have written. Or, with both the packages, you can have the responses e-mailed back to a particular address and the XML that is sent can be parsed and processed.