I'm following the instructions in
https://msdn.microsoft.com/en-us/library/office/hh361572(v=office.14).aspx but after installing the runtime, the voice, and the SDK, I couldn't figure out how to reference the Microsoft.Speech.Synthesis namespace on my Windows 7-64 bit machine with Visual Studio 2013 community edition update 4.
What's the real purpose of the SDK and how do I configure.
The installers are 64bit versions, and the voice synthesis works
PS: If you really think that my question is unappropriate here, please just put it in the comments or answers and suggest me where should I put it. I'll b glad move it far from your judgement in less than 10 hours
I believe you need to use C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.6.1\System.Speech.dll (for whichever .NET version is appropriate). It is a wrapper around Microsoft.Speech.dll. I was having problems selecting the voice, but it turned out to be just build configuration.
Related
I've been trying to install VSCommunity Edition for the last few hours with no luck. If you check the screenshot attached. You'll see that I can change the directories for installation for the first 2 requirements, but im unable to change the directory for the 3rd option (the SDK install along with others) which just happen to be the very large percentage of files. It's wanting to install over 45gb of files on my C Drive which is just a 50gb SSD.
enter image description herehttps://i.imgur.com/burFR90.jpg
I want to switch to D, and the only thing i can see fro any of the Microsoft help docs and posts is "You can change this upon fresh installation".
Which this is. I've uninstalled anything else remotely like it just to be sure.
Do any of you have any ideas or any experience with this issue, or anything i can try? I simply don't have enough space to install on C, and because of this, i can't start learning c# which is required for work.
Thanks so much in advance guys, it's really getting me worried now.
Although I can only guess why Visual Studio is locking down the SDK path, here's a few workarounds and recommendations:
In your screenshot, the installer warns you about possible performance effects of installing Visual Studio on your D drive. I assume this is because your D drive is not an SSD. Microsoft's Visual Studio system requirements document recommends that you install to an SSD, and based on community experience, this is one recommendation you really want to stick to, otherwise IDE responsiveness may be well below your expectations, especially if you decide to install extensions in future.
Instead, you might want to reconsider the set of components that you're installing. If you're only getting started with C#, you'll probably be just fine with developing class libraries, console and web applications targeting .NET Framework or .NET Core. If this is the case, you might want to go to the Workloads tab in the installer and opt out of some of the heaviest workloads (such as Mobile development with .NET). Consider only installing .NET desktop development, ASP.NET and web development, Azure development and .NET Core cross-platform development. If you only select these, your installation is going to be much slimmer.
If minimizing Visual Studio installation as shown above isn't enough, consider an alternative way of setting up your .NET development environment. For example, you can download and install .NET Core SDK and .NET Core Runtime, and use one of the two most prominent alternative code editors: Visual Studio Code or JetBrains Rider that are both quite compact.
Is there any compatibility matrix as to what Visual Studio Versions (Say, ranging 2005 - 2017) are compatible with which Windows SDK Versions?
Should any Windows SDK be fully compatible with "any" C++ compiler, or are the different Windows SDK versions bound to certain compiler versions?
For example(!), we have a legacy C++ application that is still compiled with VS2005. We found that we'd like to use GetDpiForMonitor from this application. But to use this function, would require to use the headers+libs from at least an SDK supporting Windows 8.1 (e.g. the 8.1 SDK headers at C:\Program Files (x86)\Windows Kits\8.1\Include\um)
Generally, should a developer expect to be able to switch to a newer Windows SDK version without upgrading his compiler / Visual Studio?
Please refrain from suggesting to upgrade VS: This question tries to establish what you should do when upgrading VS is not an option for now, but you want to use stuff from (and depend on) functionality only available in newer Windows (SDK) versions.
concerning the "compatibility matrix": I don't think anybody made the effort to up to create one, also I'm not sure if this is really needed.
Rule of thumb: those API headers don't change quite often, and when they do, they are usually pretty much backward compatible.
The tricky part may be to teach your older VS to get along with a new SDK, you may need to change the VC+ include/source/lib directories for your solution/project manually.
(if it complies & links in your old VS, you should be fine)
I've downloaded a Vista icon from the web for a new application I'm developing. When I try to compile it in Visual Studio 2005 C++, I get an error message:
error RC2176 : old DIB in res\XXXXX.ico; pass it through SDKPAINT
The error message seems a little misleading, I think the "old DIB" is actually a newer format that it wasn't expecting. I've never heard of SDKPAINT, and Search doesn't find it installed on my system anywhere. Microsoft claims SDKPAINT comes with the Windows 3.0 SDK, but I can't download any SDK due to incompatibilities with our firewall.
I don't really need anything Vista specific in this icon, so anything that would dump the incompatible bits would be fine.
I did a little more digging, and I found this previous question:
Which Icon Editing Software would you recommend for creating icons for apps
The accepted answer for that question suggested IcoFX. I downloaded that and used it to delete the 256x256 and 128x128 versions of the icon, and now everything's fine.
There are two more ways to achieve this in Visual Studio 2005:
replace rc.exe and rcdll.exe of your Visual Studio 2005 installation with the ones from a newer SDK (e.g. Windows Vista, 7 ...) or DDK/WDK (ditto)
or integrate the newer SDK into your Visual Studio 2005 using the respective tool that comes with the SDK
The resource compiler is the part that creates the .res files and then the usual Visual Studio 2005 linker (with the first option) or the SDK tool chain's liner links that into the binary. Meaning that even in conservative scenarios where it is frowned upon to upgrade the tool chain as a whole, this should be harmless.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
does anyone have an article how to do this ?
Since you gave no exact version of Visual Studio, let me give you the options I am aware of.
Visual Studio 2012, 2013 and 2015
Respective contemporary DDK/WDK versions: WDKs 8, 8.1 and 10 (as of this writing).
With the WDK for Windows 8, the WDK team at Microsoft finally offers full integration with Visual Studio again directly from Microsoft.
However, while Visual Studio 2017 exists in minor version 15.4 already by the time of this update, the WDK still requires Visual Studio 2015.
Visual Studio 2002 through 2010
Respective contemporary DDK/WDK versions: DDKs for Windows XP/2003 Server, WDKs for Windows Vista and Windows 7 with their respective service pack levels and the respective server versions.
Those versions were not officially supported by Microsoft to build drivers. The only worse choice to compile a driver would be a complete third-party toolchain (other than Intel's C compiler which was sanctioned by MS, IIRC).
It was considered very bad form to use the Visual Studio compilers during that period, and Microsoft explicitly recommended against it. However, C++ in kernel mode was also once frowned upon and now MS provides C++ frameworks for kernel mode. The times they are changin' ... ;)
Anyway, workarounds exist in the form of ddkbuild.bat and ddkbuild.cmd which use the DDK toolchain, but effectively allow you to integrate the resulting invocation from your "make" project inside Visual Studio. DDKWizard is a project creation wizard for both of those scripts. DDKWizard does not support Visual Studio 2010! The links to the two scripts provide a good documentation and DDKWizard also comes with a decent documentation.
To my knowledge ddkbuild.cmd is originally based on ddkbuild.bat and the HollisTech version can also trace its heritage back to that version from OSR.
VisualDDK combined with VirtualKD emerged later than the aforementioned, but is to be considered a far superior, more sophisticated solution. But your mileage may vary. In either case the integration into Visual Studio is far more complete in the latter solution.
Visual Studio 6
Respective contemporary DDK/WDK versions: DDKs for Windows NT 4 and Windows 2000.
Prior to the Windows XP DDK (now DDK is called WDK) the compiler was not included in the DDK, so you had to have the compiler toolchain installed. This would be the case for NT 4.0 and Windows 2000.
Download and install VisualDDK and you'll be able to create driver projects and debug drivers directly from Visual Studio.
The ddkbuild from OSR-Online is a nice alternative ddkbuild download link.
To build my driver i used VisualDDK in visual studio 2008. In the beginning i start debugging using my computer and virtualBox machine but when i launch the debugging process in visual studio, my virtual machine did not show me the external ip address(normally should show me 192.168.1.102 and 10.0.1.15 in DDKLauncherMonitor but it show me only 10.0.1.15 ).
I stopped using virtual machine and i decide to use real computer. In the second computer i launched DDKLauncherMonitor. And i start debugging from my first computer. I received Udp package in my second machine and also the driver.sys. But when i tried to load the driver from visual studio(First computer) nothing work. Plus this, in the second machine tell me "Windows required digitally signed driver".
There is same one meet this kind of problem and he/she can help.
create a makefile project and use the following as the build command:
pushd .
call C:\WinDDK\7600.16385.1\bin\setenv.bat C:\WinDDK\7600.16385.1\ chk x86 WXP no_oacr
popd
build -cgwiz
(obviously tweak the arguments to setenv to suit)
If you want to use DDK build and WDK use ddkbuild.bat, it is pretty good (I think most of it works still) that should have you going. Alternatively check out ddkbuild.cmd from OSR.
In VS create a makefile project. Add your sources, headers, makefile and sourcefile. Open project properties->Configuration properties->NMake->Build Command Line and write:
call $(WINDDK)\bin\setenv.bat $(WINDDK) fre wnet
cd /d $(ProjectDir)
build.exe -I
Now you can build from VS. The advantage of the makefile project: it provides you with as many configurations as you need (w2k, wxp, wnet, wlh and etc) and you can build from the DDK command line.
P.S.
fre wnet - is a sample configuration, use what is required for your project. It is good to have both fre and chk configurations.
WINDDK - environment variable with a path to the DDK root.
I have written a program in VB6. When I compile it and send it to my friend, he says it is not working. He (like me) has Windows Me.
Why my programs are not working there? Should he install something or what?
Your friend will need the VB6 runtime files to run any VB6 programs. You can find them on Microsoft's site.
You should be able to generate an installer project. There are a number of dependencies for the VB6 runtime (http://www.microsoft.com/downloads/details.aspx?FamilyID=bf9a24f9-b5c5-48f4-8edd-cdf2d29a79d5)
He should install Microsoft Visual Basic run-time files that all applications created with Visual Basic 6.0 need in order to run.
You can get it from Microsoft's Download Center.
He probably needs the VB runtimes.
But you should look into creating a proper msi installer package for you project.
There is a free one from MS to use with VB6 called the Visual Studio Installer 1.1.
Not much information to go on, if you have more, that would be helpful. I'm just guessing, but, your friend's computer may not have the VB6 runtime installed. If he's willing, he should try installing it and see if that fixes the problem.