dll Version

[becomex_jle]

Good Afternoon,

I'm trying to do version control of reports generated (dll's), I wonder how I edited versions, because all the generated dll's are coming out with version 0.0.0.0.

I await the answer.


Thank you.

[Andrew]

Hello,

Unfortunately, at this moment all the generated dll's are coming out with version 0.0.0.0. but by changing our product assemblies from one version to another you still have to delete all the old reports and recompile them anew.

Thank you.

[becomex_jle]

Hello,

Unfortunately, at this moment all the generated dll's are coming out with version 0.0.0.0. but by changing our product assemblies from one version to another you still have to delete all the old reports and recompile them anew.

Thank you.

How can I make the next DLL's leave with the version you want?

How do I edit the version to recompile. Mrt?

[HighAley]

Hello.

How can I make the next DLL's leave with the version you want?

How do I edit the version to recompile. Mrt?

When the report template (mrt-file) is compiled to the assembly (dll-file) there are links on our current assemblies. And if you upgrade to the next prerelease build, you should recompile all your assemblies.
So you will need to remove all compiled reports and compile them again when you move to the next prerelease build.

The example you could find here: http://forum.stimulsoft.com/Default.aspx?g=posts&t=142

Thank you.

[Claudio Bernasconi]

Hello Aleksey

I have the same question.
I fully understand that we have to recompile all our reports if we change the Stimulsoft-DLLs to a newer version.

My problem is that I have to define an assembly version for each compiled assembly. You can see the assembly info in the properties of the assembly (*.dll)-File.
At the moment all compiled reports have the version number 0.0.0.0.

We want to have more control over the compiled reports.

Business case:
1. Customer sends modified mrt
2. We compile the mrt
3. we test the mrt
4. we send the compiled assembly (dll) to the customer

We want to avoid that the customer uses an older version of the report assembly so we want to note which report has acutally which version number.
But if all the assemblies are always generated with 0.0.0.0 this is absoulety impossible.

I hope you can help me.

Thanks in advance.

[Alex K.]

Hello,

You can use the following static option:
Stimulsoft.Base.StiCompiler.AssemblyVersion = "1.2.3.4";

The solution will be available in the next prerelease build on next week.

Thank you.

[Claudio Bernasconi]

Hello,

I tried to realize my requirement above with the latest Stimulsoft.NET prerelease build (2012.2.1309.0) as you reported 10 days ago.
The code you suggest is compiling, but the result is still not as I expect it to be.

Please see my example below whether there is a mistake or if your solution is still not working:

Code: Select all

StiCompiler.AssemblyVersion = "1.0.0.2";
var report = new StiReport();
report.Load(GetMrtPath());
report.CompileReportsToAssembly(GetDllPath(), new[] { report });

Explanation
As I set the version number to 1.0.0.2 in my code snippet above, I expect the version number to be 1.0.0.2 in the assembly too.

Windows Explorer:


Visual Studio:


Please give me some further advise.

Thanks in advance.

[Alex K.]

Hello,

We need some additional time for check the issue.

Thank you.

[Ivan]

Hello,

The problem is solved.
The patch will be available in the next prerelease build on this week.

Thank you.

[becomex_jle]

Hello,

The problem is solved.
The patch will be available in the next prerelease build on this week.

Thank you.

Good Day,
Thanks for the answers and problem resolution.

I am awaiting the patch next week!

Regards,