In visual studio 2008 all Items in toolbox are grayed out - visual-studio

All my controls are grayed out in the toolbox when I open a Winform Project.
I have already reinstalled VS2008 and tryed all the steps indicated here, but nothing:
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/8db82810-bffd-4d07-8e50-029d2a26f7be/
If it can be related when reinstalling VS2008 I had problems with the installation of .net Framework 3.5, it was complaining about .NET 2.0SP1 missing.
I solved it installing .net Framework 3.5 SP1 and then VS2008.
At the moment I'm trying to install .NET Framework 2.0SP1 but it doesn't work: the set up stops and shows "set up error" that's it. I don't know if the issues are related.

Start from scratch and try again (starting with .NET 2.0)
.NET 2.0 (followed by SP1)
.NET 3.0 (don't remember if this is necessary before 3.5 or not)
.NET 3.5
Visual Studio 2008

I just had the same problem and resolved it by deleting *.tbd files in this folder:
C:\Users\<username>\AppData\Local\Microsoft\VCSExpress\<version>

open a package in the BID. Then the control flow items will show up. all other items(eg data flow tak) will be greyed out
Drag a control flow item. For eg, if you drag a data flow task, then edit it. Now the toolbox will show Data Flow destinations and transformations. This means, BID will show control flow items if the control flow tab is active. then you can drag a control flow items and edit it to add any task based on the control flow task you added

Related

Target Framework not installed when opening a Unity project with Visual Studio 2022

I am trying to open a C# solution that has been generated from a Unity v2020.3.19f project with Visual Studio 2022. Opening it with Visual Studio 2019 works just fine, but there are reasons I'd like to be able to open it with v2022 (such as GitHub Copilot). I did not have issues with this on my previous install of Windows 10.
Upon opening the solution in VS2022, I get the following pop-up prompt for every project in the solution:
Choosing the first option updates the target project to .NET Framework 4.8 and loads the project, but the whole file appears with red lines. When hovering over an underlined bool Property, the error shows as: `CS0518: Predefined type 'System.Boolean' is not defined or imported.
Choosing the second option opens this URL in my browser, prompting me to install .NET Framework 4.7.1 targeting pack (which was already installed via the Visual Studio Installer). When I try to install the .NET Framework 4.7.1 runtime, the installer responds with .NET Framework 4.7.1 or a later update is already installed on this computer. When I try to install the .NET Framework 4.7.1 Developer Pack, the installer allows me to choose from "Repair", "Uninstall", or "Cancel". Repairing has no effect.
I installed both versions of Visual Studio (2019 & 2022) the usual way through the Visual Studio Installer, along with the "Game Development with Unity" workload, which tells me it's installed all dependencies just fine:
Here's what I've tried so far:
Uninstall & reinstall all versions of Visual Studio through the Visual Studio Installer
Uninstall & reinstall Unity, with the Visual Studio module installed through Unity Hub (which just opens the Visual Studio Installer for me to choose which version I want to install)
Regenerate project files through the Unity Editor
Uninstall any references to .NET Framework through the Control Panel
Try reinstalling .NET Framework targeting pack 4.7.1 either from the Visual Studio Installer or manually through the Microsoft SDK website from the prompt
Nothing works for me. Any help on how to make VS2022 stop complaining is greatly appreciated.
Update 1: I found a couple of threads where people suggested simply pressing the Regenerate project files button in "Edit -> Preferences -> External Tools`. This has not helped me.
Update 2: I've tried everything I can possibly imagine, in different orders and different combinations. I even reinstalled Windows 10 to no avail. It's like Visual Studio just doesn't want to accept that the .NET Framework 4.7.1 targeting pack is installed. Please help :(
check this
https://learn.microsoft.com/en-us/answers/questions/733018/visual-studio-2022-cannot-locate-installed-net-fra.html
If you modified the value of ProgramFilesDir(x86), just to modify it back to C:\ProgramFiles(x86) can solve the problem
That is a very interesting problem, my main solution for you to first try is to make sure you are even targeting the correct .net framework in UNITY before you even build the solution. You are using the .NET 4.x, you need to go into your configuration settings and player settings in unity and ensure its not on a different version, for me, unity still defaults to .net standard 2.0. Follow the steps located here. To do so.
Another solution is to see if that first option actually gives you errors that prevent you from using unity, because I know that Visual Studio Code has problems occasionally where it tells me im wrong, my program is wrong, every life choice I have made was poor and I am poor, yet in unity, there are no errors showing in the console and I can hit play no problem. In that case I just had to rebuild a few times and fiddle with vs code until omnisharp stopped yelling at me.
Apperently I have been in a similar situation as when you were getting the error "Predefined type 'System.Object' is not defined or imported" because looking into it, I already have clicked on some of the links, try this one if that error persists. If you cannot prevent the errors to begin with, I would recommend you trying to fix the upgraded version from option one as that is more than likely going to get you the closest to a solution.

Unable to open designer for DevExpress version 8.2 in Visual Studio

I've inherited an old project which uses Devexpress 8.2.4 - so i went and installed an appropriate DXperience Subscription v8.2.4. Now, when I try to open the designer through Visual Studio 2019, I get a:
"This method explicitly uses CM policy, which has been obsoleted by the .NET Framework. In order to enable CAS policy for compatibility reasons, please use the NetFx40/LegacySecurtyPolicy configuration switch. Please see http://go.microsoft.com/fwlink/?LinkID=155570 for more information."
Then I tried to open the project in VS 2010, and upon attempt at opening the designer, same CAS policy error happens.
After editing the VS2010 DevEnv configuration file (and respective config file for VS 2019), as Thomas suggested in his answer here, my Visual Studio 2019 just started crashing during start, and my Visual Studio 2010 successfully started but it then crashed upon trying to select the designer object.
Yes, I'm trying to get this designer for Devexpress 8.2 to run in either IDE - I just need to get it to work so I can hopefully add a QR Code(is this even possible in v8.2.4???).
I just don't know how to access designer to actually graphically update the report. I did some Devexpress projects myself but using v19 and newer, but I'm having trouble now, opening this designer for old Devexpress 8.21.
Any help would be appreciated as this HAS to be done by tomorrow.
Also, if v8.2.4 doesn't support QR Code (an XRBarCode object), what would be an alternative for adding that QR Code functionality? Would I have to upgrade to newer versions - would that break something?
Thanks!

Unable to open visual basic 6 project on visual basic 8

I've created a project on VB6 at but when I am opening it on VB8, it shows the following error:
How to fix it?
As listed by GSerg in the comments, this appears to be a known issue documented in Microsoft Knowledge Base article 896292: You receive a "The remote procedure call failed" error message when you upgrade a Visual Basic 6.0 project to Visual Studio .NET 2003 or Visual Studio 2005 on Windows Server 2003 SP1 or on Windows XP SP2
To reproduce the solution here:
Cause
This behavior occurs because the VBU.exe tool has compatibility issues with the Data Execution Prevention (DEP) option.
Note: The VBU.exe tool starts when you upgrade the Visual Basic 6.0 project by using the Visual Basic Upgrade Wizard in the Microsoft Visual Studio .NET IDE.
Workaround
To work around this behavior, add the VBU.exe tool to the DEP exclusion list. To do this, follow these steps:
Click Start, click Control Panel, and then double-click System. The System Properties dialog box appears.
Click the Advanced tab, and then click Settingsunder Performance. The Performance Options dialog box appears.
Click the Data Execution Prevention tab. Verify that the Turn on DEP for all programs and services except those I select option is selected
Note By default, the Turn on DEP for all programs and services except those I select option is selected in Microsoft Windows Server 2003 Service Pack 1 (SP1).
Click Add. Locate and then click to select VBU.exe. Click Open.
In the warning box, click OK. VBU.exe now appears in the DEP program area.
Click Apply, and then click
OK. A dialog box appears that states that you must restart the computer for the setting to take effect. Click OK.
Try do divide your project to small projects(or comment large part of your project) a try again in each small project.
The idea is to find the function that is production the error.
My intuition is telling me that maybe is a DLL or OCX problem. Try to see all the external DLL or OCX calls and remove from the original project and try again the upgrading.
Most developers who move their VB6 projects to .Net do not even try to port them over. Even with third-party "conversion" software, the effort can be incredibly tedious. So much so, that most developers simply re-write the application completely. Consider it a move to a different language. In fact, some developers use that opportunity to port it to C# instead. I'm a die-hard VB6 user/fan but were I to attempt to port my 200 form accounting application, I'd just re-write it in C#. I started porting it, tried third-party conversion apps, just wasn't worth it.

How to Manually Start Visual Studio Conversion Wizard

I want to convert my .NET Website that is currently in .NET Framework version 3.5 SP 1 to 4.0. Now you get a conversion wizard when you open a VS 2008 solution in VS 2010. The wizard will convert the solution to 2010 and at the same time can convert the projects to .NET 4.0. I already converted my solution to VS 2010 but did not at the time convert to .NET 4.0. Does anyone know how to start the VS Conversion Wizard manually? According to this article it should start when you open the solution, that is not the case for me.
Thanks for your help!
The wizard converts solutions and projects from previous VS versions to the current one. It will not open again, because you already converted it to VS2010.
To change to .NET 4.0:
Right-click on the project in your Solution Explorer, and click "Properties".
Switch to the "Compile" tab.
Click the "Advanced Compile Options..." button.
Change the Target Framework to ".NET Framework 4."
AFAIK, The wizard doesn't do anything that switching target type in the project won't do. You might not get the option to back up, but you're already doing versioning, right?
To amend the Framework target, i went to the property pages of the site > build tab > updated the target framework. It re-built the web site successfully for me.

I can't add ajax controls to Visual Studio 2010

I can't add AJAX controls to VS2010 rc. I try to drag it to design view, but nothing happens, code remains unchanged. Where is a problem here? Should I install manually ajax toolbox to make it work?
Reset the toolbox and add again all your customized server control and will be fixed
Take a look at this article:
http://blogs.msdn.com/webdevtools/archive/2009/05/26/using-microsoft-ajax-control-toolkit-with-visual-studio-10-beta-1.aspx
Finally look at this: http://blogs.msdn.com/webdevtools/archive/2009/05/26/using-microsoft-ajax-control-toolkit-with-visual-studio-10-beta-1.aspx
More specifically
"The AjaxControlToolkit you can
download from the web is for 3.5 fx.
It can work with a 4.0 framework, but
you can't see some functionality such
as no smart task, or you can't drag
and drop onto a supported control, for
VS 2010 Beta2. You need to retarget
the toolkit source to use 4.0 fx and
rebuild it."
After the file has been downloaded (and extracted), you may need to UNBLOCK the AjaxControlToolKit.Dll

Resources