Comments
Sort by recent activity
SQL database We installed the new version as well. Now it is asking for a SQL database. We did never configure any SQL server and don't even have one. How can we configure SA to work without any SQL database / server? / comments
SQL databaseWe installed the new version as well. Now it is asking for a SQL database. We did never configure any SQL server and don't even have one. How can we configure SA to work without any SQL...
Hi Russel We definitely do not want to setup any SQL database just for obfuscating and merging our assemblies. So can you provide me a link with the latest version that does NOT require any SQL database? / comments
Hi RusselWe definitely do not want to setup any SQL database just for obfuscating and merging our assemblies.So can you provide me a link with the latest version that does NOT require any SQL datab...
How is the progress on this issue? the beta version is now out for several months. at what time can we expect a final (release) version? / comments
How is the progress on this issue? the beta version is now out for several months. at what time can we expect a final (release) version?
Hi Russel Thank you for providing us with the updates. This teaser shows that you really are working on this topic. I do also understand that you won't mention any date i this chat here (no matter whether you can't or you are not allowed to). Since our Productrelease(s) dates are fixed, we cannot wait for an uncertain time anymore. Also because the mergeing and obfuscating is quite a tricky thing (with lots of unexpected side effects, as we had to experience in the past), we want bring in a competitor's product (or a new version of SA) as early as possible in the development phase. So without any reliable timeframe we have to face the fact, that it might is not in time for our development and need to start evaluating some competitor's product. When the release of SA will be early enough we will consider to continue with SA for sure, but we have to be prepared for the case if not. We already tried to use workarounds like embedding the assemblies instead of merging. This works partially but brings other side effects. Some of them can be solved, but it feels more hacky than serious development. / comments
Hi RusselThank you for providing us with the updates. This teaser shows that you really are working on this topic.I do also understand that you won't mention any date i this chat here (no matter wh...
This is very sad, because lot of competitors do support this since quite some time. And since we are all software developers, we all know what is meant with "no solid time frame". Haveing a closer look at the release history of the SA Product, it does give me the impression that Redgate is focussing very much on Smartassembly product (since quite a wile). So, this forces us to switch to a competitors product. Unfortunately. / comments
This is very sad, because lot of competitors do support this since quite some time.And since we are all software developers, we all know what is meant with "no solid time frame".Haveing a closer lo...
Does the support for .netCore goes along with the support of mergeing .netstandard targeted libraries?[image] / comments
Does the support for .netCore goes along with the support of mergeing .netstandard targeted libraries?
We also suffer similar problems. For some reason this is becomming more and more an issue since about a year. We never heart of any issues like this 5 years ago (using the same obfuscation methods). So it seems that the scanning algorythm became more agressive. Currently we do not digitally sign our assemblies. I thought this might help to be treated as trustful source. Since the signing and the entire process of getting all the certificate is bound with some amount of work, I want to be sure that this really helps (so it's worth spending time on this). Does anybody knows or has expeirense, if the signing of assemblies prevents beeing treated as malware?
/ comments
We also suffer similar problems. For some reason this is becomming more and more an issue since about a year.We never heart of any issues like this 5 years ago (using the same obfuscation methods)....
Hi Jessica
Thank you for your reply. I try to create a repro that is not linked with our application (I cannot share our source code on a public platform).
In case I am not able to create such a similar scenario, would there be a possibility to share our code with redgate on a Non-Public channel?
Jens / comments
Hi Jessica
Thank you for your reply. I try to create a repro that is not linked with our application (I cannot share our source code on a public platform).
In case I am not able to create such a si...