Have to save to see design changes at runtime

Question

Hello,

Just started with VS2010. (vb)

Coming from VS2005. (i skipped VS2008)

My question is this. Why do I have to hit save before every build in order to see design changes at runtime?

Example:  I change the text on a button at design time.  I click on run and the text does not reflect the change.  But if I saved the form
before clicking run, than it does.

Also like to add VS2010 runs much slower compared to VS2005 running on the same computer.  I understand VS2010 can do more, but
a lot of times you don't need it to.

Thanks,
Mike

Answer 1

Hi Mike,

Application build on physical saved file. So it's required to save the file before build.

i agree with you vs 2010 too much slow.

Regards

Sneha

Answer 2

Hi Sneha,

Thanks for replying.  I understand I can set it up to save automatically when building but I don't want that.
What if one just wants to quickly test a change to the program but does not want to save those changes?

Is this just how it is in VS2010?  To me, this is a step backwards from VS2005.

I think VS2005 was a fantastic culmination of all the previous versions of Visual Basic.  So far, the only thing
I really like about VS2010 is the chart control.  I'll keep trying it out of course but the high hopes have vanished.

Mike

Answer 3

Hi syncbit,

This is a vb issue, I will move it to Visual Basic forum for a better support.

Thank you for your understanding!

---

Lucy Liu [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Hi Mike,

Welcome to the MSDN forum.

The default setting is “Save all changes” before building in Visual Studio 2010.  If you import settings from earlier version VS or you changed the settings, you may met the scenario.  To set the Visual Studio save all changes before building, you can Opitions ->(check show all settings) Projects and Solutions -> Build and Run -> select “Save all changes” -> Click “OK.

There’re many new and enhanced features available in Visual Basic 2010, please check this link for detailed information about What's New in Visual Basic 2010 .

I hope this will be helpful to your issue.

Best regards,

---

Shanks Zen
MSDN Community Support | Feedback to us

Answer 5

Hello,

For those searching for a likewise answer, normally what Shanks suggest is not needed, so probably in your older version is a setting done.

Also (with enough memory) VS2010 is for sure not slower that VS2005 if what Shanks suggest does not work so probably there went something wrong in your install .

---

Success
Cor

Answer 6

Hi Shanks.  As I said in my 2nd post, I know how to auto save before build.  I do NOT want to save before build.

Hi Cor.  Are you saying that you do not have to save in order to see UI design changes at runtime?  I have the same problem
on 2 seperate computers.  Although not impossible, I find it unlikely that both installations went wrong for the same issue.

Thanks,
Mike

Answer 7

Hi Shanks.  As I said in my 2nd post, I know how to auto save before build.  I do NOT want to save before build.

You can set the option to "do not save changes". However, then you're starting (optionally compiling before) the last saved version of the program. If you want to compile+start the current version, you must save.

EDIT: I don't see a problem, as Undo is always available. Isn't this an option?

---

Armin

Answer 8

I did not see any change in this although I've gone from 

2002-> 2003 ->  2005 ->2008 -> 2010 and currently 2011 Beta

I never use the save button, simply build (debug) and the data is saved. 

Moreover, I don't know whatever it would build in another situation.

---

Success
Cor

Answer 9

My situation is this.  Say you want to test an idea out.  The idea involves making many changes to code and the UI.
You do not want save these changes in case the idea does not work out.  You just want to see your idea at runtime without saving.
If the idea does not work out, then just reload the project and your back to where you're started.  I could do this in VS2005.

Is there a way to do this in VS2010?

For me, it doesn't make sense to make changes at design time only to have run time reflect the last saved state.

Thanks for your replies.
Mike

Answer 10

For this I make a copy of the project or use source code control integration in order to be able to rollback to previous versions.

EDIT: 

For minor changes you can use Undo, and for major changes I wouldn't want to experiment even without saving.

Though I admit I don't remember how it worked in 2005. I'm using 2008 and it seems to be equal to 2010 in this area.

---

Armin

Answer 11

Hello Armin.  You are not using VS2010 ???

What would be helpful now if someone could state for a fact that this is how it is in VS2010.  That you must save in order
to see UI design changes at run time.

If this is fact, then you are probably right Armin.  The best thing for me is to copy the project.

This issue reminds me of developing custom window form controls.  Where you also have to save in order to see changes at run time.
Thats why I'm thinking this has something to do with WPF.

But know one has stated that this is fact yet.

Mike

Answer 12

I think it has already been stated how it is in 2010, so I only added the information that it's the same in 2008. I'm afraid I can't say for 2005. ............. I've just tried in 2003 and it is like you describe for 2005. So it seems the behavior has changed from 2005 -> 2008.

---

Armin

Answer 13

O.K.  You are saying Yes, that is how it is in VS2010.  Good Enough.  Thanks.

Mike