I have a ANP.NET VB Project built with VS2010.
It is 2018 so I have upgraded to SQL Server 2016 and VS2017.
After opening the 2010 project file I was told I did not have the SQL Express installed that is required.
It had a link to the prompt and I have used it to download SQL Express 2014 (didn’t look for 2016 and went with the suggestion). It looked fine and I can see the project with all the files within it and are able to open it.

The real problem started when I wanted to deploy the project and it errored saying: “The target GatherAllFilesToPublish does not exist”. After pulling my hairs for hours and tyring out different unsuccesful suggestions google had to offer I came up with my own solution.

1. I created a new project with VS2016.
2. Then using WinMerege compared the .vbproj file.
3. I found that the below was missing and I copied and pasted it to where it was missing and then it was all working fine:

I needed a way to access a shared location that prompted for user name and password adn downloaded/diaplyed a TIFF image.
I had the credentials with me but to give the users a seemless experience I had to embbed that username and password.

I tired the impersonation from the link below but it generated “An error occurred while attempting to impersonate.” No matter what I tried it did not work. It couold that there was a policy that didn’t allow impersonation.

But then I realised there was more restriction because copying the file over using File.Copy was locking the file until I closed the window. I realised I could may be stream the image in the browser since the files can be accessed from the IIS server directly.
I used the below technique from the user “afetchko”:

-- command line to execute a package
-- Package model deployment was sued ins SSIS 2008 and earlier.
-- In SSIS 2012 to 2014 you could no deploy individual packages from IDE os instead you had to use DTExec.
-- Ther are multiple ways packages can e deployed:
-- 1. Server
-- 2. File System
--1. Pakcege in a Server
---------------------------
dtexec /sq MyPackageName /ser MyServerName /va
-- /va stands for validate. This si used when we do not want to EXECUTE a package but rather jsut validate it
start /min -- windows command to start an application minimised
dtexec -- if the executable cannot be found then include the whole path (whereever SSIS/dtexec is installed) as below:
"c:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe"
/file the attribute to indicate the dtsx file will follow:
"C:\SSIS\TestPackage.dtsx"
/SET --use this only if variables that need to be initiased (this is also known as parameter passing)
"\Package.Variables[User::Variable name].Properties[Value]"
;%1 -- %1 is first the argument that will be passed from cmd. To hard code this do the following:
;"hard coded value".
for second or nth parameter follow the same principle as the first one above but increase the number by 1:
/SET "\Package.Variables[User::Second variable].Properties[Value]",%2
.
.
.
/SET "\Package.Variables[User::nth variable].Properties[Value]",%n

I tried the trial software and within a few clicks I could see all my files and folders. I was amazed to able to browse the folders and files that belonged to me. I was also really amazed at how easy it was to use the software.

I went ahead and bought the software. Although it was pricey (£190.93) it exactly did what it said on the tin.