We (still) have an Microsoft Access 2000 application, installed at our customers as an ADE-file (compiled from ADP). It runs in the Microsoft Access 2000 runtime. However, every now and then the ADE-files are associated with Microsoft Access 2016, and when we run the ADE-file, it is opened in Access 2016. Then an error message appears saying that these projects are not supported by Access 2016. This can only be fixed temporarily by repairing the Access 2000 runtime setup.
Even if we run our application by including the path to Access 2000 in the batchfile, the ADE is opened in Access 2016.
I'm looking for a solution where the ADE-file association is fixed (if necessary) everytime our customer starts our application. Basically I want to know what happens when the Office 2000 setup is repaired.
Related
We have noticed that there is issue on the Citrix environment in regards to WebView2. We are trying to run office add-in inside the Outlook desktop (365) and as soon as Outlook tries to run the add-in we can see in the task manager that CPU and Memory usage spikes from 8 percent to 99 percent. Multiple instance of WebView2 processes running can be seen which consumes most of the processing power. The office add-in is not able to load at all. We have tried 2-3 office add-ins and we see the same behavior. There is no Microsoft edge installed on the Citrix .
Version
Runtime: 90.0.818.56
OS: win 10
Screenshots
Task Manager usage
Please let me know your thoughts on this.
This might be caused by hooks in Citrix which preventing the WebView2 component from starting. It can be fixed by adding the WebView2 process as an exception from all Citrix hooks. You can refer to this article to edit the registry to achieve this.
Reference link:
Webview2 application running in a Citrix environment
Is WebView2 supported in the Citrix Server
Our company would like to upload an electron desktop application to Microsoft Store, so 3rd party contractors can use it for their work. It would be publicly available.
The applications is signed and it can be built to either msi or exe format.
Is it possible to distribute our app like this?
When a new version becomes released how much time would take for Microsoft to validate our app before it can be publicly available?
The application is under development. An auto update feature is planned to be implemented. Does Windows Store provide an API to check the available versions?
Please note that we don't have any C# developers or any licenced Visual Studio instances. We would like to use Javascript/TypeScript/Angular and shell script technologies. The executable is built on linux CI server using electron.js and mono with wine. The CI pipeline is already implemented, only publishing is missing.
Thanks.
MSI and EXE installers are not supported by the Windows Store. You need to package your app as an MSIX, as explained here:
How to build an MSIX package for an Electron application
The following article talks about the steps you need to go through for publishing an app in the store. Usually. an update should be validated by Microsoft in maximum 3 days, from our experience.
How to publish your MSIX package to the Microsoft Store?
Regarding updates, the store provides it's own auto-updates service, to ensure a consistent update experience for all the apps on the machine (instead of having each up launch it's own custom updater...). You don't need to write any special code for this.
If you want to enforce some update patterns, you can use the following API to check for an update in the MS store.
Disclaimer: I work on the team building Advanced Installer.
I am looking to create an application that allows a user to update Microsoft Team Foundation Server work items when performing certain things in the app.
Has anyone done anything similar themselves and if so what is the best way to make the updates to the TFS work items from within the app?
There is a Java API which is linked below:
http://www.microsoft.com/en-us/download/details.aspx?id=22616
Other than that a few google searches resulted in the following discoveries:
http://msdn.microsoft.com/en-us/library/bb130146.aspx
The link below tells you how you can create new work items via a URL:
http://msdn.microsoft.com/en-us/library/bb822136%28v=VS.90%29.aspx
** As per jessehouwing's comment below *
This only works on 2008 and 2010 I suspect. There migth be a similar Url for 2012 and 2013, but the whole WebAccess feature was rebuilt using ASP.NET MVC instead of WebForms, so the wi.aspx no longer exists. I'm not aware of an alternative.
Visual Studio Online an Team Foundation Server 2013 are gaining more and more json based REST Api's and have recently been upgraded to support OAuth for authentication. Some of these API's are still in preview, but they're a great resource for a mobile platform client.
For older versions of Team Foundation Server and the On-premise version you can either install the OData service, or build a custom webservice that employs the TFS Client Object Model internally to create the work items.
Should you want to build your webservice on top of a non-microsoft-platform, then you can employ the Java SDK for Team Foundation Server. This will allow you to communicate directly to TFS from a Linux or Mac server.
TFS 2013.4 will be able to show more pages in full screen mode without any chrome around it.
I'm attempting to connect to TFS Preview from a C# application.
At the moment, I'm stuck trying to authenticate. I've added a reference to the TFS 2010 DLLs (I believe that these will enable me to connect, please correct me if I am wrong!) and my test case is as simple as. The URL I am trying to connect to is in the form https://MYSERVERNAME.tfspreview.com/DefaultCollection
var teamProjectCollection = TfsTeamProjectCollectionFactory.GetTeamProjectCollection(workPath, new UICredentialsProvider());
teamProjectCollection.EnsureAuthenticated();
This fails with the following exception.
Team Foundation services are not available from server https://MYSERVER.tfspreview.com/$/defaultcollection.
Technical information (for administrator):
TF400813: Resource not available for anonymous access. Client authentication required.
I had hoped that providing a UICredentialsProvider in the factory method creating the team project collection that it'd use this to provide authentication. The TFS Preview service uses Windows Live authentication, but I had hoped that this would be covered.
Pointers in the right direction greatly appreciated!
I have found that you cannot connect to TFSPreview using the TFS2010 DLL's, most likely because of the web credentials that need to be provided in order to access the site.
By adding a reference to the TFS2012 DLLs (which come with the Visual Studio 2012 RC at %PROGRAMFILESX86\Microsoft Visual Studio 11.0\Common7\IDE\ReferenceAssemblies\v2.0) I was able to successfully connect.
Download and install the Object Model for Team Foundation Server 2010SP1 and then install the Visual Studio 2010 SP1 Forward Compatibility GDR. Though this installer may look to only apply to Visual Studio 2010, it will happily update your Object Model installation if it's installed stand-alone.
For about a week now I try to set up a Dynamics AX 2009 team development environment, and keep hitting roadblock after roadblock (mostly about setting up TFS).
Are there any working installation instructions for using Dynamics AX Team Server with Team Foundation Server 2008?
Has anyone ever got this combination (AX TS & TFS) up and running?
The official installation documents are riddled with errors (saying /Sites instead of /Websites) which makes using them a real PitA! The MS certification MB6-820 and it's learning material does say nothing about distributed programming, only about single user installations.
How do others install a distributed AX dev system? Ship the servers to MS so they will handle it?
ARG! The problem seems simple:
Never ever install AX Team Server on a non-english version of Windows Server!
Some weird translators have translated the name of computer accounts. For example the system account "NT AUTHORITY\NETWORK SERVICE" is called "NT-AUTORITÄT\NETZWERKDIENST" in the german version of Windows Server.
Now a lot of programs have the name of the account hardcoded, therefore fail to find the account they are looking for, since the name does not match.
Point of the story: always install AX 2009 team server on an english version of Windows Server.