Rad Studio Rio 10.3.1, CLANG. I create a simple C++ package project for static and dynamic linking.
In previous versions of Rad Studio, for static, the OBJ files were saved in "staticobjs" folder.
See http://docwiki.embarcadero.com/RADStudio/Berlin/en/C%2B%2B_Object_File_(.obj,_.o)
Now, in Rio, this folder is not created and OBJ files (dynamic and static) are overwritten, creating a mess when instead of using 'build' I use 'make'.
Is it a bug? Do I miss something?
Related
(Apologies- I originally posted this under another case that had the same type of error message:
Microsoft.VisualBasic.Powerpacks.ShapeContainer not found)
My VS2019 project loads with 53 errors now, after reinstalling everything on a new HDD, after the Dec 2022 MS update killed my old Win 10 system.
Opening the project in VS2019 gives lots of errors like: 'Microsoft.VisualBasic.PowerPacks.ShapeContainer' is not defined
'Microsoft.VisualBasic.PowerPacks.Shape' is not defined
'Microsoft.VisualBasic.PowerPacks.OvalShape' is not defined
or 'FillGradientStyle' is not a member of 'PowerPacks'.
On the old win 10 system, all my projects worked fine. I migrated one of the projects from VS2008 to VS2019 and got it working in both versions.
Now in the new Win 10 install, I installed VS2008 again and VS2019 then copied my project folders over to my C drive.
My old Win 10 system and my old Win 7 system had a directory in Program Files x86 called 'Microsoft Visual Basic 2005 Power Packs', and inside is a folder named '3.0'; but I cannot find this anywhere (the download link provided in the other case does not exist now), so I simply copied that old directory over to my new Win 10 C:\Program Files (x86).
Opening the project in VS2019 gives lots of errors as shown above.
I also tried copying my old VS2008 version project folder over, and even opening that in VS2008 it gives these errors now.
The project references in both versions of the project already have C:\Program Files (x86)\Common Files\microsoft shared\Visual Basic Power Packs\1.1\Microsoft.VisualBasic.PowerPacks.Vs.dll and when I select this in the references window, the properties window populates and shows it is Version 9.0.0 (but RunTime Version v2.0.50727). The actual DLL file referenced shows File and Product version 9.0.30729 and says the Product Name is Microsoft (R) Visual Studio (R) 2008. So it seems like both the VS2008 and the VS2019 projects already were referencing the Powerpacks.Vs that was installed by VS2008 and they should work. (They worked in the old Win 10 system before MS ruined it).
The Visual Basic 2005 Power Packs folder was only copied, not installed (possible problem?) but that may be a red herring because the project has a reference to the VisualBasic.PowerPacks.Vs.dll.
What has happened? How do I fix it?
More Info: The Toolbox is empty, but maybe that's because it only populates once a form is open. The main form will not open because it has components from the Powerpacks, like oval shapes and containers, so I understand the toolbox not populating there. When I open my 'About' form, the toolbox populates, but the VisualBasicPowerpacks section has only a Pointer and PrintForm icon! No other shapes/components!
Just tried 'Choose Items' context menu option for the toolbox, but there are no Powerpack entries there, even though the project references include the Powerpacks .Vs.
OK, I have finally stumbled upon a solution myself. (Been working on this for a few days).
I believe there may be some incompatibility/confusion in how Visual Studio references powerpack versions.
Although my project had powerpacks.Vs referenced, and the Vs dll was there at the path, it clearly wasn't working.
Just now I opened the references window and clicked Add, then browsed to the C:\Program Files (x86)\Microsoft Visual Basic 2005 Power Packs\3.0 directory that I had copied from my old drive, selected the Microsoft.VisualBasic.PowerPacks.dll there (file version 3.0.30214.0) and clicked OK.
Now both powerpack dlls are listed.
Then I opened the main form -bingo- it loaded. The errors seemed to vanish.
I opened the toolbox and had to select the main form then another tab a few times before it loaded.
I right-clicked in the toolbox and added a new tab, named it Visual Basic Powerpacks 3.0 then right-clicked and selected 'Choose Items".
I found all the shapes (rectangle, oval, line) and selected them and clicked oK. They now are in the toolbox.
So I don't know why it didn't just work when I copied the project files over to my new install, but maybe when I opened the project it couldn't find the 3.0 and so changed the reference to the Vs version?
Maybe someone knows what actually happened. At least if anyone is caught by this problem this is quite likely what they need to do.I was lucky that I still have access to that old Powerpacks 3.0 directory, because it seems Microsoft has taken the old download page away.
I try to use MSBuild to build a delphi project, but the problem that in the version 7 of delphi, there is no file with the extension .dproj
is there any solution allow me to build it using MSBuild ?
Delphi 7 did not produce the XML project files used by MS-Build. In order to use MS-Build to build Delphi 7 projects, you'd have to generate your own .dproj file in the proper format.
It also did not come with the Borland assemblies necessary for use with MS-Build (which were placed in the %WINDIR%\assembly\GAC_MSIL folder in more recent Delphi installations), so you'd have to create your own schema that calls the Delphi compiler (both code and resource).
I am trying to set up an ASP.NET MVC 5 project in Visual Studio 2013, based on another project I have been given by somebody significantly more experienced than me. In his project, there is a References folder, with references to System, System.Core etc., together with third-party libraries. However, this folder does not exist by default in my new ASP.NET MVC 5 project. Instead, I have a folder called bin, which looks similar to References, and I can add references to dlls. What is the difference between the References and bin folders? Why does his project have one, and mine has the other? Thanks.
Your references 'folder' are assemblies (DLLs) that are referenced by your project. The reference is held in text in the project file.
The bin folder is used for compilation of your project. At compile time, the references in the project file are resolved (located for use by your project when it's running). This may be copying them from another location on disk, downloading a nuget package or using a version from the GAC. If the assembly is going to be copied down from another location it will be copied into the bin folder where all the files necessary for the application to run are stored.
UPDATE:
A different project type had been added and hence the references folder was not visible. Adding an ASP.NET Web Project into the solution solved this.
In Visual Studio 2015:
File >> New >> Project (Web Application)
A Project will have a References node when viewed through Solution Explorer in the IDE. If viewed with a file explorer (Windows Explorer) there is no Reference folder. References are stored in the project (csproj or vbproj) file using plain xml/text.
File >> New >> Web Site
A Web site does not have the References node nor a project file. In Solution Explorer right-click on the Bin folder or the root node to add References. References can be seen in the Property Pages (right-click root node).
I have a project in Borland Delphi 7. When I open the .DPR project file in RAD STUDIO XE5 it prompts an error "Framework not registered: VCL" and project not open.
I want to know what this error means. Although project is compiling and running in Borland Delphi 7.If you Google this error then there is not a single page for this error. Please help me. Thanks.
ERROR SCREENSHOT:
http://s9.postimg.org/9p6hyqodb/error.png
With the introduction of FireMonkey, a project needs to know whether it is using VCL or FMX as its underlying framework. When you upgrade your D7 project to XE5, the migration is not inserting that reference into the new DPROJ.
Unfortunately, upgrading older projects to newer IDEs has always been a flawed process full of pproblems. The best option is to simply do not do it. Create a new project from scratch and add your existing source files to it as needed.
Prior to Delphi XE and below, the DLL application's project options has these setting:
LIB prefix
LIB suffix
LIB version
However, these settings are missing in Delphi XE2. Is this a bug in Delphi XE2 IDE? Or it will no longer supported in future version of Delphi IDE?
These settings are only shown in the project options for a package project. The settings still take effect for DLL projects if written directly into the source with $LIBPREFIX, $LIBSUFFIX or $LIBVERSION. It's quite possible that the settings can be made directly in the .dproj file even though the IDE doesn't have UI for the settings.