AIMMS PRO Library

[Luis Pinto]

Hello All,

Not sure how many of you have started using AIMMS PRO (Publishing and Remote Optmization), but I have a question.

I've imported to my project both AIMMS PRO libraries:
AimmsProGUI
and
AimmsPROLibrary

They contain alot of *.amb and *.libprj files, as expected.

I maintain the project using TortoiseSVN, so I can easily tell if the files where changed or not. And recently I found out that there are changes in both libraries.

I can understand the AimmsProGUI (configuring the GUI) but I can't think of why the AimmsPROLibrary would have changed.

Any ideas?
There isn't a *.aim file to compare code.

Cheers,

Luis Pinto

www.unisoma.com.br

[Franco Peschiera]

Hello Luis,

I remember having checked the AimmsPROLibrary inside my project some time ago and it was read-only but I now see I can edit it without problem. I am not sure, though.

I do know that there is some aimms' version-specific functionalities inside that library. Maybe it has something to do with that? have you tried with previous versions of aimms?

But, yes: as of now I can confirm it is possible to edit the AimmsPROLibrary, although I do not know if that is something we should we be able to do.

regards,

Franco
--

Sent from my netBook

--
 
 

[Luis Pinto]

Thanks Franco,

A college gave me some additional information that this happened with her when she tried to do the "commit name changes".
Even though I did not change any names in the library, could be some kind of linking.

Cheers,

--
 
 

[Marcel Roelofs]

Hi Luis,

Committing name changes may be a very good explanation. The PRO library is created using AIMMS 3.10, to ensure compatibility with AIMMS version 3.10 and higher. If you use a newer version to commit name changes in your project, then the resulting .libprj and .amb will carry a new signature for the particular AIMMS version you use for your project.

Anyhow, for production usage this is completely irrelevant, as the the PRO library will be replaced by the server's version both client- and server-side.

Cheers,

Marcel

Op donderdag 29 november 2012 14:21:18 UTC+1 schreef Luis Pinto - UniSoma het volgende:

[Luis Pinto]

Thanks Marcel!
Makes sense to me now.

Cheers

--
 
 

[Franco Peschiera]

Hey Marcel,

Given the PRO library is always replaced in deployment, doesn't it make sense to make it read-only?

That way there can be no confusion while developing.

regards,

Franco

--

Sent from my netBook

--