Quantcast
Channel: Recent Questions - Stack Overflow
Viewing all articles
Browse latest Browse all 11631

Old VB project to Visual Studio 2015

$
0
0

I'm being asked to re-write/modernize/update an old VB app. The fiels are all ".vb" but there is a .sln and a .vbproj file. I try opening these in VS 2015 and it shows in Solution Explorer by name with (0 projects) and (unavailable) and "The project was unloaded"

Typically informative and helpful Microsoft text when all the tools are theirs. I digress.

How can I identify what this project is (VB 6?, VS 2010? Some flavor of .NET?). Presume I know nothing please.

How can I bring this into VS 2015 and start updating this code? I have a running version of the exe, it's a simple form app that saves some input from various controls to a file. It must be retrieving some data to populate the controls/drop-downs - there is aDataSources subfolder containing MyApplication.datasource saying it was created by Visual Studio.Net which contains:

<GenericObjectDataSource DisplayName="MyApplication" Version="1.0" xmlns="urn:schemas-microsoft-com:xml-msdatasource"><TypeInfo>WindowsApplication1.My.MyApplication, My Project.Resources.Designer.vb, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null</TypeInfo></GenericObjectDataSource>

I See nothing that identifies the source tool -some miscellaneous files - I can provide some info if requested here...don't want to burden you with gibberish.

 This code was generated by a tool. Runtime Version:4.0.30319.1

I see what looks like an installer exe Visual Basic 2010 Express.exe. Is this perhaps a flavor of SQL Express?

Any help getting me started with this would be appreciated. I would think I should be able to get this moved forward to VS2015 as a VB project - it's not a very robust app.

Opening a Solution in VS 2015 and NOT getting an error, but seeing an empty project/solution.


Update:

Here's the top of the

.sln file:

Microsoft Visual Studio Solution File, Format Version 11.00 # Visual Studio 2010 

.vbproj file:

<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == ''">Debug</Configuration> <Platform Condition=" '$(Platform)' == ''">x86</Platform>                        ...<ItemGroup> <BootstrapperPackage Include=".NETFramework,Version=v4.0,Profile=Client"> <Visible>False</Visible> <ProductName>Microsoft .NET Framework 4 Client Profile %28x86 and x64%29</ProductName> <Install>true</Install> </BootstrapperPackage> <BootstrapperPackage Include="Microsoft.Net.Client.3.5"> <Visible>False</Visible> <ProductName>.NET Framework 3.5 SP1 Client Profile</ProductName><BootstrapperPackage Include="Microsoft.Sql.Server.Express.10.0"> <Visible>False</Visible> <ProductName>SQL Server 2008 Express</ProductName> <Install>true</Install></BootstrapperPackage> <BootstrapperPackage Include="Microsoft.Windows.Installer.3.1"> <Visible>False</Visible> <ProductName>Windows Installer 3.1</ProductName> <Install>true</Install> </BootstrapperPackage> <BootstrapperPackage Include="Microsoft.Windows.Installer.4.5"> <Visible>False</Visible> <ProductName>Windows Installer 4.5</ProductName>                        ...

Well I'm electing to EDIT my post, per recommendations, but now it seems I'm at the end of my original post, so its doubtful anyone will see this.

The only snippets omitted from my vbproj file are those that identify the name of the app - for security reasons. It is a corporate app after all.Those sections don't contain anything useful in my opinion....anything relevant I included in the comments.

I received absolutely no informative messages when opening this project/ (or solution) in VS 2015. It seems happy, it shows in Solution Explorer by name with (0 projects) and (unavailable) and "The project was unloaded". I just don't get this - this is a microsoft tool opening a project created in a microsoft tool..and they can't do any better than that?

As far as enabling other dot net versions, I don't have admin access, I'm on corp computers. I recognize this is a pain for everyone...esp me.

I just can't believe I can't get anything informative.

1/29/24 - second edit

So the only tool I'm able to install is VS 2024.
Upon loading the solution file, it informs me its incompatible and to open the Migration Report that will be displayed after clicking OK. Of course, no Migration Report is made available, nor are the changes that will be made "automatically", made. So why would anyone trust Microsoft dev tools? This stuff never stops. I've been trying to trust them for 30 years and get the same endless BS.

This is the completely useless info they spew at me: (sensing a little angst here??)

UnsupportedThis version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.- , "C:\Users<userid>\dev<appname><appname>.vbproj"

Non-functional changes requiredVisual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.- , "C:\Users<userid>\dev<appname><appname>.sln"

1/29/234 - third update

Sorry, VS 2022, not 2024 installed.btw - no log file was created in the solution folder, as was also promised.


Viewing all articles
Browse latest Browse all 11631

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>