Can Visual Studio installe with ms sql server be used to modify a .net windows app? - visual-studio

I am trying to modify a .net written in visual studio 2008. However, when I loaded and try to build the website, I get a bunch of errors that several controls like firstname.text are not declared even though the app has been working.
It is possible that I am getting this error because I am using the BI version fo visual studio?
Thanks alot for all the help.

No it is not possible. If I understand correctly, you're using BIDS to modify a .NET project.
Business Intelligence Studio is a completely different program than Visual Studio (though they are based on the same editor). If you want to modify the .NET project, you will need an Instance of Visual Studio, not BIDS (Business Intelligence Developer Studio).

Related

How to access Visual Studio 2019 report designer?

Recently had need to edit some existing reports and have not been able to access the report designer in Visual Studio 2019. My application is WPF using SQLite and Entity Framework in C#. I haven't had to work with reports in a couple of years and don't have good notes from the original development. App, including reports, runs fine.
Recently upgraded to Visual Studio 16.3.0 Preview 2.0. Have SSDT included. Installed Reporting Service Projects 2.5.9. Have run Repair on VS 2019.
Perhaps need a reporting services project? Sorry don't have good notes from original development.

Is there a way to compile VB6 in 2018?

The reason I need this is I'm porting a VB6 app and I'm getting a very small difference in the arithmetic between VB6 and C#. I just need to test a couple calculations. The one I'm most interested in is how this comes out:
Round(2.24984, 1)
If that comes out to 2.3 in VB6 I'm done, it's figured out. But if not there are a couple steps leading up to that which could also be the problem.
An online VB6 fiddle would be ideal but I can install a virtual machine if I have to.
No, you cannot compile a VB6 project directly in Visual Studio 2017.
What you can do is open the project in Visual Studio 2008 and migrate it to VB.Net using the Visual Basic Update Wizard. (The migrated code will likely have errors you will have to fix yourself.) Once this is done, you can open the migrated project in Visual Studio 2017 (the current production release of Visual Studio).

Sharepoint template missing in Visual studio components

I have got 4 components of visual studio 2010 express
1)MS Visual Basic 2010 express
2)MS Visual C#
3)MS Visual basic
4)MS Visual Web Devoloper.
But none of them provide me Web part templates for sharepoint 2010. Which one would I need for this?
Do I need a proffessional? or even a Visual studio 12?
It looks like you need to have Visual Studio and SharePoint installed on the same machine in order to develop for SharePoint:
Chris Hopkins' Blog
I can tell you from personal experience this is true. I've always had to install Visual Studio onto a SharePoint server when I wanted to write new solutions for SharePoint.
If you are simply trying to edit a page layout or master page, or some other static type of content in SharePoint, you can use many tools to do so. I've successfully edited things with NotePad++ from my client PC. As long as you have the permission for the library where those things are kept, you can make changes.
I originally thought you meant developing SharePoint SOLUTIONS, by which I mean additional back-end functionality, site features, and the like.

Does InfoPath 2013 support Visual Studio 2013?

I am trying to develop custom code for an InfoPath 2013 form. I have Visual Studio 2013 Professional installed, but when trying to edit code I get the following message:
The following external components are required to edit your form code. Please install them and try again.
Microsoft Visual Studio 2012
Visual Studio C# Support
Microsoft Visual Studio Tools for Applications 2012
C# support is installed, along with Visual Studio Tools for Applications 2012.
Does InfoPath 2013 just not support VS2013?
Unfortunately No
MS has really been making some bad decisions lately
Firstly VS2013 was released so they forced people to upgrade if you want to develop for Windows 8.1
Secondly, MS have announced that they are dropping InfoPath and have yet to provide an alternate solution. Support is still available but InfoPath 2013's successor will be another solution.....i'm guessing Azure Forms or SharePoint forms, something like that
Very disappointing
As you have found, adding code to an InfoPath 2013 form requires Visual Studio 2012. I am not aware of a way to use it with any other version of Visual Studio.
Depending on what you plan to use the custom code for, you may be able to get by with the qRules library (full disclosure: I am one of the developers of this library). It contains many of the most common features for which people tend to use code within InfoPath, and you can use them simply by executing rules within your form, eliminating the need for any version of Visual Studio.
If there is a specific thing you are looking to do with code, I can tell you whether it's possible to do so with qRules, but you should open a separate question for that (and let me know here).

migrating VS project from 2005 to 2008

I have a visual studio project that was originally built with Visual Studio 2005 Professional. It makes use of some features like crystal reports and building MSI files that are no available in the freely available Visual Studio 2008. I lost my 2005 license so I opted to download the free 2008 edition, and I migrated the project. Predictably, it tells me that certain parts of the project could not be migrated, but it does allow me to work with the other parts (which is totally fine with me). The problem is, because the migration "failed" it wants me to migrate the project every single time I try to open the project.
Can someone show me the break statement for this loop?
Hope this helps Don't sweat migrating legacy .NET projects to Visual Studio 2008
Here is some information to try even doesn't help.
Make sure you open the converted project file.

Resources