InstallAware releases VS2010 .Net 4.0 Framework Runtimes....

StrataFrame Forum

Back

Home
»
.NET Forums
»
General .NET Discussion
»
InstallAware releases VS2010 .Net 4.0 Framework Runtimes....

InstallAware releases VS2010 .Net 4.0 Framework Runtimes....

Author	Message
Terry Bottorff	Terry Bottorff posted 13 Years Ago Post Details Share Post
Group: Forum Members Posts: 448, Visits: 12K	Should you add the individual Assemblies that are needed for Strataframe or use the Merge modules? That is when you are trying to build a Setup with AI? TIA.
	Reply Like 2
Edhy Rijo	E Edhy Rijo posted 13 Years Ago Post Details Share Post
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	I never used the merge modules. I add each assembly to the IA Assemblies page. Edhy Rijo
	Reply Like 2
Terry Bottorff	Terry Bottorff posted 13 Years Ago Post Details Share Post
Group: Forum Members Posts: 448, Visits: 12K	Good enough. Thank you so much.
	Reply Like 2
Terry Bottorff	Terry Bottorff posted 13 Years Ago Post Details Share Post
Group: Forum Members Posts: 448, Visits: 12K	A couple of follow up questions. Do you get the assemblies out of the \Program Files (x86)\MicroFour\StrataFrame\Assemblies? Do you put the assemblies in the GAC on the Clients machine or copy them into the TargetDir? TIA.
	Reply Like 2
Edhy Rijo	E Edhy Rijo posted 13 Years Ago Post Details Share Post
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	Terry Bottorff (5/28/2011) Do you get the assemblies out of the \Program Files (x86)\MicroFour\StrataFrame\Assemblies? Yes and no. Since I develop multiple projects, I rather have all my runtime assemblies in a common folder for all projects, separated by versions, this way, if I get a new version of SF, it will not override the previous assemblies and still will be able to re-create my setups. Terry Bottorff (5/28/2011) Do you put the assemblies in the GAC on the Clients machine or copy them into the TargetDir? Yes and no. For some standard applications, I use the TARGETDIR, but for others which are more specialized, I use the GAC just to add a level of confusion for somebody trying to copy the application to another computer and make it work illegally, I mostly do this for fun, as far as know, some customer have tried but adding some good security code protect the investment and of course my lunch <smile!!!> Edhy Rijo
	Reply Like 2
Terry Bottorff	Terry Bottorff posted 13 Years Ago Post Details Share Post
Group: Forum Members Posts: 448, Visits: 12K	Thank you. When I right click on my Project and go to Properties and I look at the Compile tab I notice that Configuration is set to Active(Debug). Do I need to change the Compile from Active(Debug) to Release and then Publish my Project before I try to create my setup with IA? TIA
	Reply Like 2
Edhy Rijo	E Edhy Rijo posted 13 Years Ago Post Details Share Post
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	Hi Terry, Yes, you should build your IA setup based on the Released version of your application not the debug. What I do is that once a released version is ready to ship out, after compilation I copy all the assemblies to another folder from which serve as the image source for the IA setup. Edhy Rijo
	Reply Like 2
Ivan George Borges	Ivan George Borges posted 13 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Edhy Rijo (4/19/2010) Hi guys, For those of you using InstallAware they just released an update to add the .Net 4.0 Framework runtimes, here are the links: Here is the web based installer Here is the offline installer - containing all files inside a single 391MB payload And here is the forum link for more details... Hey Edhy. A bit late, but thanks for posting this. I faced an issue with VS 2010 Service Pack 1 and SqlServer.SMO referencing .NET Framework 3.5, so as Keyth and Marcia have already done it, I had to recompile SF under CLR 3.5 and now I will have to make sure my installations test this pre-requisite on the clients machines. Since I own Installaware 7, I didn't have these CLRs ready for installation. Your post directed me to the right place! Thank you.
	Reply Like 2
Edhy Rijo	E Edhy Rijo posted 13 Years Ago Post Details Share Post
E Group: StrataFrame Users Posts: 2.4K, Visits: 23K	Hi Ivan, Ivan George Borges (12/9/2011) A bit late, but thanks for posting this. I faced an issue with VS 2010 Service Pack 1 and SqlServer.SMO referencing .NET Framework 3.5, so as Keyth and Marcia have already done it, I had to recompile SF under CLR 3.5 and now I will have to make sure my installations test this pre-requisite on the clients machines. Since I own Installaware 7, I didn't have these CLRs ready for installation. Your post directed me to the right place! You are welcome, but just to be clear, I have not seen the issue that requires me to rebuild SF under CLR 3.5. Here is my configuration: VS2010 SP1 All my projects are using .Net 4.5 runtime. SF source is as distributed by MicroFour, only the DevExpress solution is rebuild, but using 2.0. InstallAware 9 R2. I install the SQL SMO2008 with a custom IA script, I don't remember if I created it, or get it from somebody else couple of years ago, if you need it I can send it to you. Edhy Rijo
	Reply Like 2
Ivan George Borges	Ivan George Borges posted 13 Years Ago Post Details Share Post
Group: StrataFrame MVPs Posts: 1.9K, Visits: 21K	Yeah, I would also be fine if I hadn't made some customizations to the SF source code (don't tell "anyone" I did it!). But as I have done so, I do need to recompile it, and then I hit the error I mentioned before right in the DBEngine project, which uses SMO. This is because the SMO now makes reference to the CLR 3.5 System.Core ( http://connect.microsoft.com/VisualStudio/feedback/details/651546/microsoft-sqlserver-smo-could-not-be-resolved-because-it-has-an-indirect-dependency-on-the-framework-assembly-system-core-version-3-5-0-0 ), and then VS2010 SP1 will complain about it, since SF is compiled under CLR 2.0. That is where I got stuck and had to change the source code to compile under 3.5.
	Reply Like 2