Deploying vb.net App with inno script

I have a vb.net App attached to a SQL MDF database.  Inno Script supports .net 45  The database is version 852.(2016+) MsSQLLocalDB will only run version 782database.   since inno script doesn't check for or install dotnet46, or the local db version, how do either:
ADD the new files to connect to this database or
Is there an existing script for the new version of dotnet.

OR should i consider a different installer.  This is not an area of my expertise and this will be installed on many different machines as a local APP.   I could use some advise.  Thanks
williamj67Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vadim RappCommented:
So, what do you need to install with your product - dotnet 4.5, or sql server express, or both?
0
williamj67Author Commented:
The problem i have is that INNO only has dotnet4.5 included i really need to install 4.6 if i do that, i need to install the localDB for 4.6 as well to insure that the database will run.  The 2014 version of MSSQLLOCALDB won't connect to the database and i really don't have a way to reduce the version on the database.  i need an MSI file for MSSQLLOCALDB for 4.6 and dot net 4.6 script for inno.
0
Vadim RappCommented:
I'm not a pro in innosetup, but looks like this script is the answer to dotnet 4.6:

https://gist.github.com/canton7/72104b1fb154442d5a9ba937fd3ee781

That said, regarding deployment of Microsoft frameworks and such, the best practice has always been to avoid bundling them with the product, mostly because they often get their own updates, security fixes, and such, so one year down the road their installation is likely to be different from what it is today, which means that you will have to follow up and update your installation whenever Microsoft updates theirs. Installations of Microsoft own products usually check if prerequisite framework is installed, and if not, they tell the link to download from, and exit.

As an alternative, you can install Microsoft package by command line called from the product setup like this:

<path>\NDP462-KB3151800-x86-x64-AllOS-ENU.exe /passive /promptrestart

More details at https://docs.microsoft.com/en-us/dotnet/framework/deployment/deployment-guide-for-developers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
williamj67Author Commented:
I think it makes sense for me to keep the dotnet separate as you mentioned.  Thank you for the link.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.