This question is a follow-up of this one:
My situation is the following: I would like to do some development. There exist tools who offer syntax highlighting, but the official tools seem not to, as you can see from those images:
Syntax highlighted excerpt of previous answer:
What do I see when I do this:
According to my colleagues, there was syntax highlighting in the past, but as a result of some upgrade, there wasn't anymore, and they have no idea what happened.
Does anybody know how to get syntax highlighting in Process' release 11.6 AppBuilder and corresponding tools?
For your information, for syntax highlighting purposes, I'm currently using the Notepad++ one, as described in this URL.
edit after question about configuration
Hereby an excerpt of the configuration, as requested:
Configuration File: C:\Progressx86\OpenEdge\PROGRESS.CFG
Company Name: Microsoft
Product Name: Progress Dev Studio OE
User Limit: 2
Expiration Date: None
Version Number: 11.6
Machine Class: KB
Port Number: 31
There are similar entries of the product names "OE Workgroup RDBMS", "Client Networking" and "Translation Manager".
(For security reasons, I've removed any referenced about IDs, like serial numbers, I hope the control numbers are not what you're looking for?)
Thanks in advance
OK - different scenario. You do actually have a Progress Developer Studio license (Eclipse based IDE). In that case, Progress is not providing the color-coding in the classic AppBuilder I'm afraid. That was a st...d Product Management decision years ago to save some pennies on 3rd party royalties.
If you're licenses are coming from the OEDK or PSDN subscription, you can install OpenEdge Studio in parallel - as the subscription contains both products. That's the license that provides the color-coding for the AppBuilder.
If you're not using Progress Developer Studio (Eclipse based IDE) now and will not do so in the foreseeable future, you could reach out to Progress Software and apply for a license change.
I'm afraid this is more a commercial issue than a technical issue.
Syntax highlighting in the 64 bit AppBuilder (prowin.exe, not prowin32.exe) was introduced in OpenEdge 11.7
https://knowledgebase.progress.com/articles/Knowledge/000042690
If you're using a 64 bit OpenEdge Studio license, the simplest fix would be switching to a 32 bit license - if you can still get that from Progress Software.
Related
I installed Latest Version of Developer Toolkit for vs2015 and after that when i use toolkit to connect to CRM, after click on connect button it does not do anything. no error, no success action,
i delete every Cache data and every Temp data and Clear my solution but nothing change,
do you have any idea? help me please because i want to develop custom workflow step and develop plugins with this toolkit.
As far as I know, Microsoft's Developer's Toolkit has been dormant for quite some time.
Current options are:
Jason Lattimer's Developer Extensions
Which is also on GitHub.
Or the commercial add-on XrmToolkit, which has a 30-day free trial.
If you go with Jason's solution and you're looking to do early bound development you might want to also look into XrmToolbox's Early Bound Generator by Daryl LaBar.
The XrmToolkit includes its own proprietary proxy class generator.
I can't seem to find anything related to this so hopefully you guys can help me out.
I recently had BI Publisher installed for me by our company IT. Usually i would prefer to do this myself (I'm a software engineer who worked tech support before), but company policy dictates that IT needs to install all company programs.
Anyways in BI Publisher I now have the issue that if i double click on a field i don't get the BI Publisher Properties as I should (Word 2007), instead I get the standard 'text form fields' properties. Is there anyway to fix this without IT getting involved since whenever I give them my laptop I end up being unable to work for quite a while.
Thanks in advance
Make sure your security settings have macros enabled.
If you had any older versions of BI Publisher desktop, that were not removed before installing the new version, you may have to remove both, and reinstall the version you want.
Make sure the version you are installing is compatible with the version of Word you are using. Oracle is really bad at compatibility.
Make sure you have a compatible version of Java installed too.
Do you see the add-in tool bar in the ribbon?
After read lots of other posts and could not find an answer, I ask if someone had the same problem.
I wrote two versions of the same APP: one for free and another paid version.
Hours after publish both, only the paid version can be found in google play. The free version does not "exists" if I use the search tool (using web or devices), but it is PUBLISHED in developer console.
The most weird is the fact I also can't find the application clicking "More From Developer"! Where the free version is?!
Comparing the Manifest of both, they are the same except the package and name.
Any one can help? Thanks!
Answering my own question: there is a bug in the new layout of developer console. I added two languages in my application: English, Portuguese. But instead of create two different languages, developer console added English twice. With the old interface I removed the second language and create a new Portuguese translation again. It worked!
I have been using Visual Basic 5 since it was first released until a couple of years ago.
I re-installed it on each new laptop I bought and downloaded the service pack each time. I think it is SP2 for VB5 I need.
But having not touched it in two years I have now just installed it on a laptop to modify an app. However, it seems that Microsoft no longer offers the service pack for download.
And on opening my projects i get repeated messages for each frame telling me I "don't have the license to use the control in developer mode".
What is this error and how do I get the service packs?
If you port to VB6, you shouldn't have to make very many changes.
If you port to any version of VB.Net, you will find that the changes are rather extreme. An automated tool will try to do some of the work for you, but depending on how your code was written and what VB5 features you used, you will probably find that you manually need to fix up most of the changes that were made.
The biggest problem is that some of the VB5 features don't have direct equivalents in VB.Net. Do any of your forms use control arrays? You CAN do something at least vaguely similar in VB.Net, but the conversion tool doesn't know about that, so converting them will have to be completely manual.
FYI, Microsoft service packs are available in two forms. The normal update process figures out what patches are needed on your computer, then downloads them and installs them. But there's also an "administrative" version that downloads every change that MIGHT be needed, in one package. That package doesn't automatically install - when the download is complete, you have to manually start it running. The admin version is intended for system administrators, who might have to apply the same patch to dozens / hundreds / thousands of computers on a network - you shouldn't have to download the same data over and over.
The admin service packs won't help you with VB5, of course (unless you find someone that downloaded the VB5 service packs and held on to them). But if you end up going to a new version of Visual Studio (or VB), and you think that it's likely that you'll keep using them more than 6 months or so past the end of Microsoft support, you might want to get in the habit of downloading the admin service packs and archiving them somewhere. It might prevent problems like this in the future.
The licensing issue is referenced on Microsoft knowledge base
http://support.microsoft.com/kb/181854
A fix is available, downloadable from the same place.
Note : if you are running Windows Seven, you need to run VisualBasic in elevated mode.
How do I let Microsoft know about a problem I've found in one of their core library routines? Do they have a central repository to report these things?
I am not a member of Microsoft Development Network (MSDN).
Or should I even bother?
There is no official way to report bugs to Microsoft for an end-user. If you are participating in a beta program for an upcoming release, the beta program includes a bug-reporting channel. Otherwise, if the bug causes problems that you want to get resolved, you can call Microsoft support, and they will help you solving the problem (be it by providing a patch, or a work-around); if the problem turns out to be caused by a bug indeed, they will refund the costs of the support call.
Microsoft does have a central repository (perhaps separate ones per product), but this repository is not accessible for the general public.
If it's a documentation bug (or if the documentation should call it out), you can get good results with the Feedback links in MSDN library. You can report bugs in Microsoft developer tools (among other things) by signing up at connect.microsoft.com.
If you're sure you've found a bug in a core library routine, you can raise a PSS (support case. It'll cost you money, but if it turns out you're right (and they issue you a hotfix), I think that they refund the money.
I've never been so confident that I've found a bug that I'm willing to make that gamble.
I don't know why ChrisN took back his answer. I saw it earlier today when he had it up, He said:
You can report bugs on the Microsoft Connect website (I've done this in the
past). You don't have to have an MSDN
subscription.
I had not heard of the Microsoft Connect website, but when I used the search box there to search for "Registry Unicode", the first entry listed was a bug very similar to the one I encountered. And clicking through on that entry led me to look at the conversation that appears to be Microsoft people addressing the issue, passing it on to appropriate people and escalating it as necessary.
I have no experience with the Microsoft Connect website, but if it turns out to be as promising as it appears, this may be the answer to my question.