Im reading some books on Visual Studio and SQL Server and I am not
done... so im sure somewhere in the next 1000' pages I will come across
these answers (hopefully), but I was wondering if someone can give me a
quick blurb answer just so the thoughts in the back of my head are
partially answered as I read on.
1. When using sql express ( or microsoft sql (higher version) ) how
hard is it to create a new "setup.exe" or a "patch" when you have
database changes as part of your application.
Example of this: You have a package written and installed ( not using
click once ). So now you develop some new things, and also make some
new database changes. Is it pretty easy to just create a "patch.exe" or
something that updates the users' exe to the new one and also the
database? I have switched on learning the sql side of things, but im
from an mdf generation where these updates were done through code to
insert / delete / update new tables and columns within the database. Im
just wondering ( not a complicated answer ) on how its done now.
2. Last night one of the chapters talked about developers getting an
msdn subscription instead of purchasing VS2005 ? ( if i understood
correctly ).
What really is the point of an msdn subscription. It seems that you pay
1000 bux each year for the same product, + get some beta software that
you can only test on anyway?
3. Im currently using the vb2005 express...and am assuming its best to
hold off on buying vs2005 professional and wait for the vs2008 ( orca )
released and buy that - or until Microsoft allows for a free upgrade to
ORCA when vs2005 is purchased so close to a 2008 release date.
-I am learning and writing some small apps, but i have time - and can
survive for what I need in the express till then.
Thanks,
Miro
done... so im sure somewhere in the next 1000' pages I will come across
these answers (hopefully), but I was wondering if someone can give me a
quick blurb answer just so the thoughts in the back of my head are
partially answered as I read on.
1. When using sql express ( or microsoft sql (higher version) ) how
hard is it to create a new "setup.exe" or a "patch" when you have
database changes as part of your application.
Example of this: You have a package written and installed ( not using
click once ). So now you develop some new things, and also make some
new database changes. Is it pretty easy to just create a "patch.exe" or
something that updates the users' exe to the new one and also the
database? I have switched on learning the sql side of things, but im
from an mdf generation where these updates were done through code to
insert / delete / update new tables and columns within the database. Im
just wondering ( not a complicated answer ) on how its done now.
2. Last night one of the chapters talked about developers getting an
msdn subscription instead of purchasing VS2005 ? ( if i understood
correctly ).
What really is the point of an msdn subscription. It seems that you pay
1000 bux each year for the same product, + get some beta software that
you can only test on anyway?
3. Im currently using the vb2005 express...and am assuming its best to
hold off on buying vs2005 professional and wait for the vs2008 ( orca )
released and buy that - or until Microsoft allows for a free upgrade to
ORCA when vs2005 is purchased so close to a 2008 release date.
-I am learning and writing some small apps, but i have time - and can
survive for what I need in the express till then.
Thanks,
Miro