| Author |
Message |
AntoineC
Joined: 16 Jun 2010 Posts: 8
|
Posted: Fri Jun 18, 2010 8:51 am Post subject: Failure during build |
|
|
When building my project with SmartAssembly 5 with the "I want to use strings encoding with improved protection" option, SmartAssembly build process fails with the following exception:
System.IndexOutOfRangeException.
Is this a known issue?
I have enabled all other settings in SA and the build works perfectly. The generated application is working without issue. I have a problem only with this option.
Thanks,
Antoine |
|
| Back to top |
|
 |
Alex.Davies
Joined: 02 Dec 2008 Posts: 335 Location: Cambridge, uk
|
Posted: Fri Jun 18, 2010 2:51 pm Post subject: |
|
|
Hi Antoine,
No, no-one has come across that issue before to my knowledge. I have an error report from you though, so we should be able to work out what's happened.
Thanks, _________________ Alex
Developer,
Red Gate .NET Tools |
|
| Back to top |
|
 |
maitpg1
Joined: 09 Jun 2010 Posts: 3
|
Posted: Fri Jun 18, 2010 5:59 pm Post subject: Also seen it |
|
|
I have also seen this message.
I can't be any more help, though. I've had the product about a month, and I've been testing all sorts of things and working issues between v4.2 & v5, and I have long since forgotten what I was doing to cause it or to make it go away. |
|
| Back to top |
|
 |
melvyn.harbour
Joined: 15 Mar 2010 Posts: 28
|
Posted: Mon Jun 21, 2010 2:34 pm Post subject: |
|
|
That's the advantage of the error reporting - we can see a lot of the internal details at the point where the failure occurred, so we should be able to track the problem down fairly easily, and make sure that it's fixed in a subsequent release.
Mel _________________ Melvyn Harbour
Project Manager
.NET Tools Division |
|
| Back to top |
|
 |
Paul.Martin
Joined: 03 Feb 2010 Posts: 83 Location: Cambridgeshire
|
Posted: Wed Jun 23, 2010 4:27 pm Post subject: |
|
|
In case anyone else has this problem, Alex had a look into the matter. He found that SmartAssembly was getting confused counting when it was trying to add the improved version the string encoding to strings when they are in the global namespace and class ("<module>").
The fix should be included in a forthcoming update (provisionally 5.2)
The two options I can suggest in the meantime:
- Use the standard version of string encoding
- Move the strings from the global namespace and class |
|
| Back to top |
|
 |
|
|
All times are GMT + 1 Hour
|
| Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group