I am using Intraweb version 14.0.0 on C++Builder 10.2 Tokyo.
I have constructed a test application using TIWServerController and TIWApplication.
When I run the application it shows the controls on the web browser, but I am not being able to get access to the same application using another web browser window of the same kind.
How can I use IntraWeb to serve the same application to several users from different locations of the same local network ?
Thank you very much.
Jayme Jeffman
I have found the problem. The version of IntraWeb (14.00) which was added to C++Builder 10.2 Tokyo community edition does not work the same way as it does on the paid version which has the 14.2.10 attached to the paid edition of C++Builder.
I have asked to a collegue of mine who has the paid edition to build the same test application I have made and everything is now working fine. Including the port number that now is always the same set in the IWServerController instead of start each time with a new one.
Related
I have one small doubt regarding Microsoft.Xrm.SDK.dll. Recently I received an email from Microsoft saying they are turning off support for any Microsoft.Xrm.Sdk.dll version less than 8.2.
I am using Dynamics CRM 2016 (App version: 8.1.1.1183, DB Version: 8.1.1.1183), and SDK client to connect to this CRM. This SDK client uses Microsoft.Xrm.Sdk.dll v6.1.
I want to know will it continue to work or do I have to make change in the code and upgrade the dll?
Thanks
This is probably related to ACS deprecation (which is only applicable for online orgs):
See: https://blogs.msdn.microsoft.com/crm/2017/05/29/update-dynamics-crm-client-sdk-version-to-avoid-calls-to-acs/
With the deprecation of Azure Access Control Service (ACS), you should
modify the SDK authentication code by removing all references to ACS.
Effective from Microsoft Dynamics CRM Online 2016 Update 1 (v8.1.1)
and Microsoft Dynamics 365 (v8.2), we removed Live ID support and ACS
dependencies on the server-side. It is required to update the
references in all client side components by updating the SDK.
For custom applications you need to make sure you have the correct version of the SDK.
Custom Application(s) – If you have developed a Web/Windows/Console
application that is interacting with Dynamics CRM
Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the
Team Blog site to determine which version of the SDK you need to
download.
Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service
you are using. If you are uncertain which .NET version your solution
is using, contact your development or engineering teams.
Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest
version of the SDK dll.Replace Microsoft.XRM.SDK.dll with latest
version of SDK dll
I recommend you to go through the MSDN blog
Without knowing when & where (which CRM version your) project started & staying in 2016 now and what’s your future project plans (whether sustenance mode or stay current), could not comment on action.
As a general practice, do a pilot with an upgrade in separate copy/sandbox & see. Then plan for code Update & sdk upgrade in Live.
I'm developing a windows phone application. I have a version of my app in windows store. I know how to find the version of package I'm developing, but i want to find programmatically the version of my app in windows store,so i can compare and if the version store is bigger than the version of app user has, i want to make a notification and tell him that a newer version is available.
Thanks in advance!
Beginning with WP8 you can query the Store using windows.applicationmodel.store.listinginformation but sadly this does not include the version.
There is no public Windows Store API that provides this info. So you'd have to either scrape the info yourself or connect to a 3rd party API that provides alreasy scraped data. Solutions outlined here: windows store api to access metro and phone apps information
Wait but why?
If you only need to provide your app the latest version code, just store it in a JSON file hosted on your backend, or alternatively, if you're feeling fancy, create a dedicated webapp that checks for updates.
I am working on a Windows Phone News Client and recently we changed some of the APIs. For that some of the older versions of my app is crashing heavily as there are format mismatches.
My question: Is there any way available to restrict users of previous version (suppose version 1.0.0.0) using that particular version? Or, force them to download the latest version of app (suppose version 1.0.0.1) from store? Does Windows Phone Store have any built in feature for this purpose?
Please guide me. Thanks.
As far as I can see, there is no such feature in Windows Phone Store to accomplish your requirement. When update available user will be notified, but the update won't get installed automatically without user action.
You should implement logic to restrict user in the application it self. For example, upon application start up, check current version against latest version in server, then close the application if it isn't up-to-date.
I installed Microsoft SharePoint and Project PWA on Windows Server 2008 R2.
When I want to open Library in Windows Explorer, I randomly get an error:
Your client does not support opening this list with Windows Explorer
When I open IE it's working for 1st and 2nd time, but after some clicks it's not working anymore and I need to restart IE and then it normally works for couple of times.
When it not working through Sharepoint it also not works via \server\DavWWWRoot\PWA and oposite.
I'm searching through the web for weeks and didn't find any solution.
Do you have any idea what should be wrong here. Any suggestion is welcome :)
I had the same exact issue with Windows 7 and explorer view. The following steps resolved the issue for me:
First - be sure that the Web Client service is running (run>services.msc).
Next - In I.E. check Tools>Internet Options>Security>Local Intranet>Sites>Advanced and add the site that you want to use explorer view with.
This finally fixed it for me. I hope that you have already found a solution to this issue! I was surprised at how difficult it was to find a solution to this problem!
This error message is a symptom to a billion different problems.
I solved this problem when I realized my XP32 box could do this just fine with IE8. So I reverted to IE8 in 7x64 (you have to do it by uninstalling updates for IE until you're back at 8) and it didn't work. The build versions were different and on the 7x64 "about" box it said IE8 was using 256-bit cipher while in XP32 it had 128-bit. That to me was a hint that there may be 64-bit issues even when you run the 32-bit executable.
Then I found this hotfix so I reinstalled the windows update for IE10 and then installed this hotfix. Now I'm able to open the TeamCenter site in question in windows Explorer. IE10 reports it's version 10.0.9200.16686. I cannot guarantee that it was the hotfix alone (and not also the reinstallation of IE10) which fixed it. But I'm willing to bet it was the hotfix alone.
In XP I found it impossible to then map this network location to a drive letter, as mapping doesn't like URL's. However in Windows 7 you can transform the URL so that it is interpreted as a Windows share. If the URL of a given folder is of this form:
https://somesharepoint.com/folder1/folder2/folder3
you can also access it as
\\somesharepoint.com#SSL\DavWWWRoot\folder1\folder2\folder3
and, in this form, it can be mapped to a drive letter.
I do have issues at that point that even with IE10 open and logged in to the site I see some random time-out like problems and I get kicked off (and prompted to log in again in IE10). My situation is complicated because the site I'm accessing requires an Exostar token to log in, so I have to log in via website no matter what.
If it helps any one do the steps suggested above:
Make sure to use 32 bit internet explorer (program files (x86)/internet explorer).
Like was mentioned above Web client must be started.
You may also need to add your site to trusted sites in internet explorer.
Make sure enabled protected mode in internet options is disabled.
This is what finally fixed it for me: Check "Keep me signed in" on the login page. This was the key for me. Will not work without it checked in my case.
I had the same symptoms, and it turned out I don't have a root site collection. Creating one solved this for me.
Summarized the troubleshooting steps here:
http://letitknow.wordpress.com/2012/07/22/your-client-does-not-support-opening-this-list-with-windows-explorer-error/
There can be multiple reasons for it.
One could be using IE x64 version. It won't work there.
Secondly, check out this blog:
http://blogs.technet.com/b/asiasupp/archive/2011/06/13/error-message-quot-your-client-does-not-support-opening-this-list-with-windows-explorer-quot-when-you-try-to-quot-open-with-explorer-quot-on-a-sharepoint-document-library-in-office-365-site.aspx
I experienced the same problem as well.
And I found out that if none of the above options are working, and if you work in an organisation, maybe the proxy is blocking the "Open with Explorer" option.
I did the same, and removed the proxy and it worked just fine.
this fixed it for me ( however in windows server 2008 you may need to install desktop experience i think its called)
After you log into windows go into services then restart the WebClient then see if you can use explorer view without the error " your client does not support. blah blah blah" if it does work then. make a batch file that says:
net stop webclient
net start webclient
then make a scheduled tasks that runs that batch file at start up. Have it run as a user with administrative rights, make sure you tell it to run even if user is not logged in. it should prompt you for the password of the admin account you selected. this worked for me with windows 7.
I found online where the error can occur intermittently with SharePoint 2010, however I think the SharePoint version is irrelevant. They said the client polls for a SharePoint root site and that the error occurs if one isn't found.
We have not seen the error since I created a root site even though we’re only using WSS3. Our errors began when we changed clients to Windows 7. So in our case it sounds like the issue could be the root site polling due to an IE8 security change in Windows 7.
SOLUTION:
*you on x64 bit machine* so solution is that there is no problem but you are using the wrong IE shortcut.
There are different IE types you can use (just type Internet Explorer in start search bar) and you will see..
Internet Explorer (64-bit) - won't show any sharepoint add-ons
Internet Explorer (No Add-ons) - won't show any sharepoint add-ons
Internet Explorer - only this will show sharepoint add-ons and will
work so basically make sure you always use this version of IE
I'm looking for suggestions on keeping a program that is running on a network updated. Installation consists of 15 users, each have the program on their local pc, but they all access same date from sql server.
I am looking for a clean method that would allow me to update one folder on the network and for each computer to get updated when they run the program and the programs sees a later ver on that folder on the network. (Obviously I can do this inside the program itself since it won't allow being overwritten while opened.)
You should have a look at
ClickOnce is a deployment technology
that enables self-updating
Windows-based applications that can be
installed and run with minimal user
interaction.
Using ClickOnce Deployment in
VB.NET
ClickOnce - A new VB.NET 2005 Deployment Tool
ClickOnce Deployment for Windows Forms Applications
ClickOnce Deployment in .NET Framework 2.0
Another option is to create a second program that will check the network for an updated version of your application. Let's call this program "updater.exe".
You can run updater.exe on system startup like Adobe Reader or Sun Java do.
Or, when your application is started it can load updater.exe. If updater.exe finds an update, it can close/unload your application, download the newer version, restart your application and close itself.
astander's answer above is correct, you can use ClickOnce for this. Another option is creating this application as a web application.
Web applications basically work the way you described, the application's files reside in a web server, all the users connect to it using a browser, and to update the application you only need to update the files in the server.