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 7 years ago.
Improve this question
We are developing a web application using C# and Angular.
The client and the server communicate with JSON to send datas.
My problem as a fronted developer is : When they change the model's variable's name, the client doesn't still work anymore.
Example :
if the model is:
public class Person
{
public string name;
}
In the Angular Application I use exaclty the same structure when I receive the JSON:
<h1>{{myJson.name}}</h1>
And sometimes the back-end developers change the variable's name, I need to return to update the client side, and I loose big time in debugging with that.
Any tutorial or blog or something to know what's the best way to use data between server and client ?
Thanks a lot !
If the external shape/behavior of code changes, then any code which uses it must also change. This is the definition of a "breaking change".
I suspect the ideal way to avoid this problem is to have a set of automated tests which validate the code. If someone makes a breaking change, tests will fail. At that point the build is considered "broken".
If possible, it may be worth implementing a kind of "check-in rejection" system where the source control doesn't allow a check-in of a build which fails to compile or fails tests. This is native functionality in TFS, but may not be a feasible option for many systems.
Failing that as a technical barrier, at that point it's pretty much a team-enforced barrier. Someone breaks the build, they are responsible for fixing it. Sure, sometimes that person has left for the day or maybe there's some other reason why you or another team member needs to "clean up after them", but it should be clear from the source control history that they broke the build.
If you're spending a lot of time fixing things which other developers broke, that's less of a technical problem and more of a team dynamics problem. Automated tests bring visibility to that problem. Developers shouldn't be able to check in code with failing tests, either through a technical barrier or a social one.
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 7 years ago.
Improve this question
We have a custom CRM solution that among several things handles our call-center. That is, each call-center operator gets a queue of people (potential customers) to call based on a number of configurable rules. For example, certain operators only handle certain types of users. Call queues are ordered by call-time taking timezones into account.
EDIT: Operators dial manually. We're currently not interested in automating this.
Now we want to replace this call-center subsystem because it has several bugs, its implementation is very messy and the original developers left years ago.
So we're trying to decide whether to build this ourselves from scratch or integrate another CRM (like SugarCRM) for this specific task only.
But I'm totally ignorant about SugarCRM. Does it provide such a module? Is the SugarCRM API flexible enough to handle different rules to select and order a call queue? We're a .NET shop so we don't want to mess with SugarCRM's code. Or is there any other similar CRM you can recommend for this task? Where do I start?
Thanks in advance
If you are a .NET shop, is there a reason you've not mentioned MS Dynamics CRM ?
While there is a cost associated with it, there is a huge amount of customisation you can do, and if, at some point, you decide to look at telephony, it'd be straightforward to do that too.
I have built CRM systems that integrate with a PBX based dialing system. We had a lot of success with home grown systems.
I would advocate a build from my personal experience for the CRM portion.
What you are asking about, however, is the Dialing side of the system. This can be built as well - the API's for the Dialogic cards lend themselves nicely to .Net implementations. Now that is going to take some work, and most cheap dialers have some decent functionality out of the box to do what we want it to do.
It is when you get to complex functionality that they give up the ghost and by that time you are already so far tied into them that going into a new system is not feasible. I have seen this happen over and over again too.
If you have decent talent on hand, I would advocate writing the dialing system as well if you see yourself having to handle issues more intricate than your basic off-the-shelf dialer can handle.
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 3 years ago.
Improve this question
I have a small classic asp site and I am concerned that a client may stop paying me. The site is on their server, so I basically want an "off switch" in the event they stop paying me. I couldn't think of a good way to do this as they have a tech person who has access to the server, so any code I write to stop the site would be easily found and changed in the classic asp site (there aren't many pages).
So we had thought of maybe obfuscating the 2 main class pages so that they won't be able to edit the pages easily and we still have code to stop the site functioning. My questions are:
What is the best option for obfuscating classic asp code (if anyone has done this before)?
Is there another option that maybe we're not thinking of?
Thanks for any help you can provide!!
I think your energies are better placed on setting milestones in your project that are tied to payments. This ideally is done in increments so that neither party feels at a disadvantage with regards to the amount of work done / amount of money paid.
Obfuscation is easily removed and decoded, generally.
Remote checking for a security license opens a security hole for the application, and also can be defeated relatively easy.
Putting in code that "self destructs" if some action or code is not removed is also not great practice.
Licensed software is a little bit different in this regard. It sounds like you're building a bespoke system that you will simply hand over to the client at the end. If that's the case, putting in mechanisms to disable that system that only you control is not a great way to build trust. They may be violating trust if they fail to pay, but your disabling of the website actually gives them an additional incentive NOT to pay you, and consider you as a programmer willing to put in a Trojan Horse into the code.
The real problem to solve here is not in code, but in project management. A social not a programming problem.
This is a hard problem, and a great one for StackOverflow. I wish you well in sorting it out.
You're in Australia right? You have a small claims court system? If you've delivered what you were obligated to code for them, you shouldn't have a problem collecting.
I'm pretty sure that programmers have gotten sued or even charged criminally for this sort of thing; the courts see it as "hacking" into a client's site and breaking it over a payment dispute. Be careful.
I believe the best way would be to simply have it call your own server for some critical piece of data. That way you can restrict that service if / when their subscription does not tally with your desired business model.
It does depend a lot on the site, but there will always be something you can return from your own server to keep the site active. Also this does give you the advantage you are not disabling their server but your own if it goes wrong.
hope that helps
There is a tool from Microsoft called Script encoder that encodes a script into garbage, though it's fairly easy to get the original back..
Why not put some of the business logic into a VB6 component? That's valid optimisation and obfuscation in one. They could decompile such a DLL, but it's a lot of hassle.
More importantly, you need to consider who owns the code, regardless of what you do at this point. The link below is a discussion on code ownership in freelance situations (without a contract), and I think that the accepted answer defines the issues rather well: https://stackoverflow.com/questions/111815/freelance-work-with-no-contract-who-owns-the-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 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.
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!