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
I've already tried EazFuscator and Dotfuscator but are bad! I was able to easily read the source and pay it, and frankly I'm tired of the people that I copy the software.
I ask you which obfuscator use, at least to protect all the software by beginners.
From the great Joel Coehoorn ... you can read more here
How can I protect my .NET assemblies from decompilation?
One thing to keep in mind is that you want to do this in a way that makes business sense. To do that, you need to define your goals. So, exactly what are your goals?
Preventing piracy? That goal is not achievable. Even native code can be decompiled or cracked; the multitude of warez available online (even products like Windows and Photoshop) is proof of that.
If you can't prevent piracy, then how about merely reducing it? This, too, is misguided. It only takes one person cracking your code for it to be available to everyone. You have to be lucky every time. The pirates only have to be lucky once.
On another note, I would recommend SmartAssembly by RedGate. Ive used this before and its great compared to others. Please note that like any obfuscator, you cannot stop someone cracking your software if they are determined to do so.
You can get more information here...
http://www.red-gate.com/products/dotnet-development/smartassembly/
Related
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 5 years ago.
Improve this question
I need to move some changes from database a to database b, and some from b to a. Every comparison tool I've used requires you to pick a direction first and if you want to go the other direction, well then you get to wait for it to completely re-compare all over again.
Also the tools I've used don't allow you to make changes on the fly. If I see something I need to update, I've got to go update it using SSMS and then come back to the tool and re-compare all over again.
What I really want is a tool that works just like a text diffing application (BeyondCompare, WinMerge, etc.).
I've thought about trying to write my own app to do this so many times but it's a big undertaking so I always say "nah, it's not worth it". Well I've finally decided to give it a shot but I just want a final word on 2 issues:
1) Have I overlooked some amazing product that already does this? I've searched but haven't found anything. Would hate to waste a lot of time if someone has already done it though.
2) What Diffing api would be best suited for this type of application?
The best tool for doing this action is from redgate called sql compare.
http://www.red-gate.com/products/sql-development/sql-compare
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 5 years ago.
Improve this question
I like good documentations for source code, but I hate the documentation comments in the code. I found solutions to separate the code from the documentation for other languages, but not for Rust. So, is any solution to separate the source code from the documentation in Rust out there?
Edit: Many years have passed and this below answer is no longer true. See the comments.
I'm afraid there's none. I am following Rust ecosystem and I have never seen even a mention of anything like that. On related note, I think the comments should be in the code, and if you writing open source code in Rust I'd advise to stick with the standard ways of doing things, just for the sake of other people. Eg. I am a vivid advocate of tab indentation as opposed to spaces ("Indent with tabs, align with spaces"), yet because Rust community settled on (clearly inferior :) ) spaces, I use spaces in my Rust projects. It doesn't fit my preferences, but after getting over it, it makes mine and other people lives easier when cooperating.
As a workaround, I would suggest making your editor just aggressively fold comments.
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 5 years ago.
Improve this question
Background
There is a hardware project going on. A hardware accelerator has been being developed by a team of students but there is no general documentation.
There are READMEs here and there, some docxs and in-code (Verilog, C and Lua) comments, but nothing else. The code is written with Vim, versioned with Git and Markdown is our friend, even if we are not on Github (yet).
Since this “thing” is growing, I feel the necessity of writing down something (user manual? developer notes?) but I don't know where to start.
Question
When someone feels the urge of documenting his project, where does it start?
More specifically, what are the generally accepted criteria to do it and what are the best tools?
My hypothetical answer
We quite clearly need both a developer and user manual. One with details of the algorithmic solutions, the other... like for monkeys.
About the tools, I believe that something like a Github Wiki would work fine, but (1) we are not on Github and (2) wouldn't be LaTeX a better way of writing stuff in order to publicise it, eventually. I know we can get our Markdown rendered in a printable way with http://www.cocowrite.com/, but is it the most efficient solution? LaTeX would be a nuisance for collaborative editing and online HTML publishing.
A partial answer can be found here: “What tools are used to write documentation?”.
Second part of the answer can be found here: “What amount of documentation is needed for a non-trivial one-man software project”
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 4 months ago.
Improve this question
Is there any RDBMS Schema design assistance tool, which can check/critique the data-base design, suggest amends to improve normalization, suggest constraints, discover potential conflicts etc. ?
Note the idea is not so much of a diagramming tool, although if it is integrated in a diagramming tool, it would be swell. Alternatively, it could be something that works with SQL schema.
Preference would be towards FOSS tools.
I'm sure if you posted your questions here people will jump on it with some insightful opinions. I doubt you can really develop a program that can do this... it really depends on what you're building. Normalization does not determine "good" design.
TOAD is the most popular tool for this (sorry, not OSS).
http://www.quest.com/toad-for-oracle/
It'll help you find some issues with your design, but it's not a magic bullet either. Other than TOAD I haven't seen any other tool that comes close to being useful as opposed to manual auditing of the schema. Any other ideas?
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
In order to improve my open source project, I need testers. I have created my project independently, so up to now I have been the sole coder and tester. I have tested the thing to death, but as we all know it is dangerous as a developer to test your own code. I'm looking for ideas on how I can get some other eyes to exercise it.
To clarify, I have released it on sourceforge and posted it on freshmeat, dzone, reddit, etc.
Are you looking for "testers" or "users"? There's a world of difference.
A tester uses his time and energy to find your bugs. How many people are willing to do that? At a rough guess, I'd say zero.
A user uses your software to solve his problems. He reports bugs to you because he thinks that you might fix them for him. So you've got to find people with a problem, and convince them that your software will fix it.
One thing you'll need is lots of documentation. A 1-minute screencast, in-depth API, and everything in between. You need to persuade someone that, "If I use tox, I will totally rock!"
That's your tester.
Release an early version, announce it on freshmeat, and wait for the world to beat a path to your door?
Go to where the testers are. Find sites where testers go. http://www.stickyminds.com, local QA groups (like mine) http://redearthqa.blogspot.com/ or local recruiters that have QA people looking for experience.