I have created program using MSVC++ that besides it's main task calls WCF server functions. Under Windows 7 and Windows 8 everything works fine and I got several problems with Windows XP:
On some machines I have error that webservice.dll is missing and program doesn't starts. Why some Windows XP installations contain webservice.dll while others - not? How to install required dll?
On Win XP computers that has webservice.dll sometimes programm just crashes without any reporting. After recompiling program without WCF client code program runs fine. What might be starting point to look for the problem?
Windows Web Services API (WWSAPI) is an operating-system component of Windows 7 and Windows Server 2008 R2 or later versions of Microsoft Windows.
On Windows XP you need to package it with your app. The reason it works on some boxes is probably caused by one other installed application that uses that the WWSAPI as well.
The final version of the Windows Web Services API for Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 is now available
In contrast to the past pre-released version of this API, this final version release can be used in production code and redistributed with the final versions of the product. Because of this, the final version is only available to companies who agree to terms of Windows Master Redistribution License Agreement (MRLA). To acquire the redistributable installers for this release and a copy of the Windows MRLA for review, please email a formal request.
Partially copied and adapted from Windows Core Networking blog, from Ari Pernick, dated Oct 9th, 2009.
Related
I'm studying Microsoft COM technology from the book Learning DCOM 1999. I am puzzled with its Hello Universe sample program in Appendex D. The code is available here.
This sample contains a HelloClient.exe and a HelloServer.exe. They can be run on different Windows machines and HelloClient.exe is able to remotely call server's exposed IHello interface.
I tried HelloServer.exe on Windows XP and the HelloClient.exe on Win7 successfully call into the remote object.
However, when HelloServer.exe is run on Windows 7, the remote client always fails on CoCreateInstanceEx(CLSID_Hello, ...) with 0x80040154 (Class not registered).
So I think there must be some change since Windows Vista/7 that causes the failure.
Then what is the change, or, what am I missing?
BTW: I compile the code using Visual Studio 2010 SP1.
I have a set of applications for which we want to add Windows 10 support. I expect some users to run them on Windows 10 Enterprise LTSB (Long Term Servicing Branch) and others on Windows Pro CBB (Current Business Branch). Sometimes our users keep machines off LANs for security reasons, so we can't assume much about when updates will be applied. We also can't dictate that our users get all Windows updates as a first step to troubleshooting. (It's a case-by-case basis.)
We have not historically needed to consider special editions of Windows. In the past we have tested these apps on Pro versions of Windows and Standard versions of Windows Server.
I'd like to relate this question to precedents, but I don't see an obvious correlation. For example, would an LTSB vs CBB machine comparison be more like Windows XP SP1 vs Windows XP SP2 (which was a breaking difference for us) or is it more like Windows 7 Pro vs Windows 7 Ultimate (which is insignificant for us)?
I did not see any distinctions between LTSB and CBB in Windows SDK googling and we don't expect to depend on any of the Windows apps currently excluded from LTSB. I think the main issue is whether there might be windows behavior that is changed in a "Feature Upgrade" that a CBB machine might get and an LTSB machine might not yet have. (As opposed to a "Service Update" that I hope they would both get, if receiving updates automatically.)
I am just curious if there is a way to package up a Windows 8 Metro application to distribute it to others with the Windows 8 Developer Preview installed? It would be nice to be able to allow someone to just download and install, rather than requiring them to install VS'11 Preview and compile the code themselves in order to test out / use a Windows 8 Metro application that I've built.
Is there a way to distribute a compiled Windows 8 Metro application for others to test/use since the Windows Store is not yet live?
This would likely be useful for testing Metro apps on non-development machines even after the Windows Store is live.
Each machine that wants to install the application will need a developer license. See this page for some details.
When you have your app ready:
select Store->Create App Package
Select Build a package to use locally only
Follow the prompts
This will create a package in whatever folder you specified. You should be able to copy that to another developer-licensed machine and install it.
There will be a batch file called Add-AppxDevPackage in the directory. Running it will install the app. It must be run as an admininistrator.
Distributing apps outside store is possible after complying to the prerequisites listed in this MSDN article. It also covers the process of application installation using PowerShell. Though it appears quite complicated, note that MSIs work fine for Windows 8 metro apps so you can probably enclose the installation process into one small instalator.
From the article
Requires Windows 8 Enterprise Edition, and must be joined to a domain, and the domain must have the Allow all trusted applications to install Group Policy setting.
for Windows 8 Professional, and Windows RT, or a non-domain joined machine, you must buy a sideloading product activation key from Microsoft
the application must be signed by a key that is trusted by the computer
Once you've purchased your sideloading product key from Microsoft, add the sideloading product key:
>Slmgr /ipk <sideloading product key>
To enable side-loading, enable the following guid:
>slmgr /ato ec67814b-30e6-4a50-bf7b-d55daf729d1e
To add an application, from a powershell prompt:
>add-appxpackage C:\app1.appx –DependencyPath C:\winjs.appx
Windows 8.1 Update
According to the latest announcements by Microsoft the next update to Windows 8.1 will allow all the devices running the Pro version to sideload applications without sideloading activation key. So far this has been the case only for the Enterprise version. Bare in mind that the machine will still need to be a part of the AD domain. Additionally, if you still run a previous version but you're part of any of the below programs:
Enterprise Agreement
Enterprise Subscription Agreement
Enrollment for Education Solutions (under a Campus and School Agreement)
School Enrollment
Select and Select Plus
You'll be granted the enterprise sideloading rights starting on the 1st of May 2014. Otherwise you'll still be able to sideload but will need to buy a sideloading activation key for 100$ (that's a one-time charge for an unlimited number of devices).
If I recall correctly from the white paper, then a Windows 8 Metro application can only be installed by consumers from the App Store.
However there will be a way provider for developers (as explain by Stave Rowe) and a way for corporations to installed Windows 8 Metro application directly, I expect the corporation method will be by using Active Directory (group policy), but may be limited to some editions of Windows 8.
You can distribute the Windows 8 App package and deploy the same using the Side loading process
Refer this link for more details about side loading
http://technet.microsoft.com/en-us/library/hh852635.aspx
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.
I have a windows application that acts as a WCF Service that I developed on a 32bit Windows Server 2008 box. I have tested the application and everything works fine when running it from my development machine, as well as from my 32bit workstation. However, when attempting to run the application on a 64bit Windows 2008 Server, the application does not run, and a Windows Error Report is generated stating that the application stopped working. I have attempted to build the application on my 32bit Development Workstation, targeting both x86 and x64, to no avail. The only time I can get the application to run is if I comment out the code that starts the WCF Service. So my question is, do I need to dev and/or build this application on a 64bit workstation to allow the application to run on a 64bit machine?
Ok, I figured it out, nevermind...needed to run the app as admin on that server...
You need to configure http.sys to accept your urls using the httpcfg utility. There is a similar thing for Windows Server 2003.
How to add a URL ACL and avoid AddressAccessDeniedException in Windows Vista
Httpcfg Examples: Internet Information Services (IIS)