| Author |
Message |
Alex.Davies
Joined: 02 Dec 2008 Posts: 335 Location: Cambridge, uk
|
Posted: Wed Nov 10, 2010 12:24 pm Post subject: SmartAssembly 6 EAP build 119 download |
|
|
Red Gate is brewing a new version of SmartAssembly.
New in this build:
- New, more powerful control flow obfuscation
- Consent system for feature usage reporting
Download here:
http://www.red-gate.com/MessageBoard/viewforum.php?f=116
Please post any comments or feedback in this forum.
Last edited by Alex.Davies on Thu Nov 18, 2010 7:17 pm; edited 2 times in total |
|
| Back to top |
|
 |
madmaxor
Joined: 04 Nov 2010 Posts: 1
|
Posted: Mon Nov 15, 2010 12:48 am Post subject: |
|
|
| Hi Alex.Davies, the download link seems to be broken |
|
| Back to top |
|
 |
Alex.Davies
Joined: 02 Dec 2008 Posts: 335 Location: Cambridge, uk
|
Posted: Mon Nov 15, 2010 11:48 am Post subject: |
|
|
So it does. I swear it was working when I put it up.
I'm fixing it now. _________________ Alex
Developer,
Red Gate .NET Tools |
|
| Back to top |
|
 |
Uniwares_AS
Joined: 11 Oct 2007 Posts: 132
|
Posted: Mon Nov 15, 2010 4:21 pm Post subject: |
|
|
Are there going to be any changes to the build system in v6?
Improvements to how the MSBuild task accesses the database?
Better support for build configuration? |
|
| Back to top |
|
 |
Alex.Davies
Joined: 02 Dec 2008 Posts: 335 Location: Cambridge, uk
|
Posted: Mon Nov 15, 2010 4:42 pm Post subject: |
|
|
We don't have any specific improvements planned for the MSBuild task. What did you have in mind? Sorry if you've already posted something I've forgotten about, please link to it. _________________ Alex
Developer,
Red Gate .NET Tools |
|
| Back to top |
|
 |
Uniwares_AS
Joined: 11 Oct 2007 Posts: 132
|
Posted: Mon Nov 15, 2010 5:17 pm Post subject: |
|
|
Use of build variables and parameters comes to mind , evaluation of macros, etc. all inside the .saproj file, which in the end means no more project file but a .target file instead. Would make it really a lot easier to setup SA projects with outputs from other results of the build process, depending on build type.
And also that little problem of multiple invocations of the SA build task which reuses the database connection instead of having one for each instance would be nice to see improved (yes, i still have this problem occasionally and its always related to other extensions)
I would also like to be able to configure SA without having an assembly ready. Often I know what I want but I need it to happen in the build pipeline, and not always I have the intermediate executable available. In those cases I have to create the project by hand and cant use the GUI. |
|
| Back to top |
|
 |
Uniwares_AS
Joined: 11 Oct 2007 Posts: 132
|
Posted: Wed Nov 17, 2010 1:59 pm Post subject: |
|
|
Oh yes and PLEASE: make the GUI remember and use paths already selected to resolve references. Nothing more annoying than having to select 10 times a folder for 10 assemblies which are in the same folder. Argh.  |
|
| Back to top |
|
 |
Uniwares_AS
Joined: 11 Oct 2007 Posts: 132
|
Posted: Wed Nov 17, 2010 6:52 pm Post subject: |
|
|
Another thing that comes to mind now is the HintPath. A project specific HintPATH would be great instead of a assembly specific reference.
Something like
| Code: |
<SearchPath>$(ProjectDir)/References</SearchPath>
|
would be just great to find assemblies used in the current project without specifying each one with full path. |
|
| Back to top |
|
 |
iosub
Joined: 19 Oct 2010 Posts: 19
|
|
| Back to top |
|
 |
Alex.Davies
Joined: 02 Dec 2008 Posts: 335 Location: Cambridge, uk
|
Posted: Thu Nov 18, 2010 6:19 pm Post subject: |
|
|
Not yet. It's getting close to the top of the pile now though. _________________ Alex
Developer,
Red Gate .NET Tools |
|
| Back to top |
|
 |
|