New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow access to persisted variables from related bundles #3704

Open
wixbot opened this Issue Jul 10, 2012 · 4 comments

Comments

Projects
None yet
5 participants
@wixbot
Collaborator

wixbot commented Jul 10, 2012

Burn currently only allows persisted variables to be accessed from the same bundle, allow these to be accessed from related bundles so they are available for upgrades e.g. if the install location is changed it should be persisted for an upgrade so the install location doesn't have to be manually changed.

Originally opened by nsleigh from http://sourceforge.net/p/wix/feature-requests/697/

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Sep 15, 2012

Collaborator

This creates a very tight binding to the data file. We'd need to do this very carefully.

Collaborator

wixbot commented Sep 15, 2012

This creates a very tight binding to the data file. We'd need to do this very carefully.

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 24, 2013

Collaborator

Originally changed by barnson
Area changed from bootstrapper to burn
Release set to v4.x

Collaborator

wixbot commented Oct 24, 2013

Originally changed by barnson
Area changed from bootstrapper to burn
Release set to v4.x

@wixbot wixbot added this to the v4.x milestone Dec 20, 2015

@gclpixel

This comment has been minimized.

Show comment
Hide comment
@gclpixel

gclpixel Feb 13, 2017

Hi,
is this feature still on your roadmap?

I've created a custom BA and this has the rights to read the former written rsm file with the saved variables. But I need to know the serialization format of this file and also which variables are saved with their types.

gclpixel commented Feb 13, 2017

Hi,
is this feature still on your roadmap?

I've created a custom BA and this has the rights to read the former written rsm file with the saved variables. But I need to know the serialization format of this file and also which variables are saved with their types.

@robmen

This comment has been minimized.

Show comment
Hide comment
@robmen

robmen Feb 13, 2017

Member

It's not closed but it's not assigned to anyone either. That means it's waiting for a WIP to be written and implemented by someone.

Member

robmen commented Feb 13, 2017

It's not closed but it's not assigned to anyone either. That means it's waiting for a WIP to be written and implemented by someone.

@robmen robmen self-assigned this Oct 26, 2017

@barnson barnson assigned jchoover and unassigned robmen Oct 26, 2017

@barnson barnson modified the milestones: v4.x, v4.0 Oct 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment