I am using Monodevelop for writing D programs, and whenever I open a file I get this error. Does anyone know about this?
It is a common problem that happens when user has an older version of MonoDevelop (now Xamarin Studio).
You have two solutions:
Get the version of Mono-D that works with the MonoDevelop version you have installed on your workstation.
Install the latest Xamarin Studio version, and the latest Mono-D.
How to do the #1 is little bit tricky - you have to find the plugin file, and follow the "install from file" procedure. It is explained somewhere on Mono-D blog and I believe there is a link to a page where you can see all versions...
Related
TWO very related questions in this post.
How to install 6.5 & 6.5.1 in eclipse(more detail below)
Intellij Toolbox last version supported is 2019.2.4 but looks like codeone plugin doesn't support it?
In intellij, codenameone 6.5.1 simulator is not working(font is way too small) but it's working in 6.0.0 with my eclipse(from when I played with it 6 months ago). I am trying to test out each version to see what the latest version is that is not broken for me(hopefully at least 6.5). When I go to eclipse marketplace, there is no upgrade and it just shows this for codename one (eclipse verison 2020-06 as I clicked update all)
I don't see a way to download a zip file and install it in eclipse and only see the install from marketplace method here
https://www.codenameone.com/download.html#step2
Is there a zip download for eclipse somewhere I can try of 6.5, then 6.5.1?
I also want to try to downgrade my intellij version but we also need the latest so I grabbed the new intellij toolbox but this only goes back to version 2019.2.4. The compatibility list on codenameone plugin is such
I wonder about that first line for 6.5.1. A dot release and they added support all the way back to 2016 version which 6.5 didn't have? Seems like a type. Also, 6.5.1 did not work with latest intellij and honestly getting worn down in playing the version mismatch game of uninstall/install to see what works and doesn't work (it's just takes quite a bit of time).
If anyone can post a STABLE list of IDE version / plugin version they are using, I would LOVE to know that <- If I know that, I will just jump to that. I can cope with eclipse or intellij. In fact, eclipse debugging is way better and intellij refactoring is way better so I am always torn between each.
Trying 2019.1.4 with many versions next.
Figure this out finally. Not sure exactly but this repo https://github.com/deanhiller/codenameOneExamples
now works with latest intelij 2020.1.3 !!
I have a C code (pretty old one) that I tried to run in VS17 and am getting this error:
The build tools for Intel C++ Compiler 17.0 (Platform Toolset = 'Intel C++ Compiler 17.0') cannot be found. To build using the Intel C++ Compiler 17.0 build tools, please install Intel C++ Compiler 17.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
I am not including the code as it is old and big.
Can someone please suggest what the problem is?
It means your project configuration was done with an old version of Visual Studio.
I suggest you follow the VS suggestion: at the solution pane, right click on the project/solution and select 'retarget solution'. This will change your solution/project configuration to the current visual studio you use (2017).
As the project/solution files will be overwritten by the 'retarget' process, it worth copying the solution/project files (or even the entire solution
directory) before starting the 'retarget solution' process, so you can revert to the previous state for troubleshooting etc.
An example:
I'm want to build an old version of librdkafka, which was originally built with VS2010, and I want to use VS2017.
when looking at the solution explorer pane, you can see all projects has "(Visual Studio 2010)" title near them, at the left side of each project name.
Now I right click on the solution, and select 'Retarget solution':
At the dialog box, you get, click OK, and that's it.
I've seen that there is a lot of literature about this topic, but nothing specific to VS2017.
I've created an application that works properly on my PC, but when i move it to another one it doesn't start at all.
I've tried to install the latest version of .Net Framework (4.7.1) but it looks like the new pc doesn't recognize it. In the framework folder below directory reference assemblies it's missing, only 3.0 and 3.5 are available.
I have seen that there is another method to let the application run: static linking of dll. But I didn't find the way to do it with VS2017. There isn't section c++\c where flag /mt instead of /md. I know that my application will be larger, but I don't mind.
I have developed a .bpl package with some components. I did this in C++ Builder XE7 and to install it I could just select "Install package" (or something similar) by right clicking on the .bpl project (in the project manager).
Now I have updated to C++ Builder Tokyo (10.2) and there is no alternative to install/uninstall the package from the project manager.
Has this function been moved/renamed? Do I really have to do it manually?
EDIT:
I solved it. For anyone having the same problem, It seems like the import from XE7 into 10.2 doesn't work that well. I opened it in 10.1 and there the install option became available. Then I opened that project in 10.2 and everything went fine now...
Make sure Win32 platform is selected when you want to install. Since IDE is a Win32 app, you can only install win32 components in it. The other platform targets just use components blindly. This causes other issues that Embarcadero has put on back-burner for way too long for example they have not done anything about RSP-10456 since I reported it when XE8 was in beta.
I built a WPF application in VS.NET 2008 using ClickOnce deployment. It ran great on any machine that had VS.NET installed, but my business users received an error: "Unable to install or run the application. The application requires that assembly Microsoft.Windows.Design.Extensibility Version 3.5.0.0 be installed in the Global Assembly Cache (GAC) first."
I was surprised to discover that this dll is not part of the standard .NET 3.5 SP1 client installation, but somehow, my application thought it was needed. I checked my Publish tab for the project and it showed up as a prerequisite.
Oddly enough, I was able to just remove this (and all of the other Microsoft.Windows.Design.* dlls) and it just worked everywhere. I removed them from my project entirely, and everything was fine.
Can someone explain why the VS.NET 2008 project wizard forced these to be included in the project, and more importantly, why ClickOnce thought they needed to be on the client machine to run?
This is just a curiosity question, but I'm sure I'm not the first to be bitten by it. Hopefully, this post will at least save someone else the headache.
Try to remove all references to *.Design.dll. In my case it was WPFToolkit.Design.dll.
This is old and the OP is gone, but I ran into this today, so I thought I'd mention that my solution was removing a reference to one of the WPFToolkit references that ends with .Design.
I had referenced System.Windows.Controls.Input.Toolkit, but also had a reference to System.Windows.Controls.Input.Toolkit.Design, which should not have been there. Removed it, and all was right with the world again.
A way to find out the code that is loading the assembly is explained here:
http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/755272f6-0e79-4a6d-ae50-4412d0f2bc4c
I found that I was using the SelectionCommands.Clear property which is inside the Microsoft.Windows.Design.Interaction namespace inside the Microsoft.Windows.Design.Extensibility Version dll.
Beats be why this dll isn't included in the .NET 3.5 install.