Implict Theme via Build_WPF45_Xamlless.bat shows no controls

Justin

Hello, I am attempting to build licensed copies of 2015_1_0401 WPF to use with a WPF 4.5.1 application.

I built the assemblies from Source Code using the instructions for creating Licensed builds and can see in the JustDecompile that the licensed strings were present and working properly. I used the aforementioned bat file to build on a clean VM of Windows 8.1 x64 with VS 2013.4 which is only used for building purposes. I don't have anything installed on it other than VS.

Unfortunately, when I create a basic WPF Scenario project and add references to my custom built Xamlless DLLs, I find that no windows are visible at all. I have followed the help instruction on applying Implicit themes.

To validate where the problem existed, in my built DLLs or elsewhere, I created a simple project with one main window and one Telerik Window and a button on the main to open the telerik window. Same issue existed. So I removed the references to my custom built DLLs and replaced the references with the "installed" Xamlless DLLs from my Program Files directory and everything worked perfectly.

So a few questions on this as I have now spent hours trying various approaches and building/rebuilding/new test projects etc:

1. the BAT build results in 5336 Warning(s) and 0 Errors. That seems very high to me--I am for 0 personally... is this high number expected?

2. the resulting Binaries folder contains two directories: WPF and WPF.NoXaml. The WPF.NoXaml directory contains a child called "Dev."

Which of these is the right binaries directory to use?

3. Does Telerik WPF installation need to be performed on my VM in order to build these BAT files properly?

4. What could be wrong with the build process--it is very straight forward, extract the Source Code, alter the Licensing files, and run the given Bat script.

Petya

Regarding the folders with binaries that are created, you can think of the WPF folder as a "working" directory. Basically, running the Build_WPF45_Xamlless.bat executable will create the WPF folder and eventually copy all files related to the use of the control with implicit (NoXaml) styling in the WPF45.NoXaml folder. If you then run the Build_WPF45.bat, again the WPF folder will be populated with files and eventually all files you need to use in your project will be copied to the WPF45 folder. In short, you need to use the files in the WPF.NoXaml\Dev directory.

As to the warnings, there isn't anything irregular on your end and this is the amount of warnings that we are observing as well. The majority of those are related to missing XML comments of public members, but there are others too. We are continuously trying to resolve as many as possible for each new release, but I'm unable to commit to a specific time when there will be zero warnings.

Justin

I am seeing that Documents.Core.dll is completely missing from the WPF.NoXaml\Dev directory as of latest build when in all prior builds (2016.2.503, 2016.1.217, and before) it was there as described in the quoted post.

Now, however, the only place I see this and some other DLLs is under the WPF directory.

Please let me know.

Petya said:Hello Justin,

Regarding the folders with binaries that are created, you can think of the WPF folder as a "working" directory. Basically, running the Build_WPF45_Xamlless.bat executable will create the WPF folder and eventually copy all files related to the use of the control with implicit (NoXaml) styling in the WPF45.NoXaml folder. If you then run the Build_WPF45.bat, again the WPF folder will be populated with files and eventually all files you need to use in your project will be copied to the WPF45 folder. In short, you need to use the files in the WPF.NoXaml\Dev directory.

Justin

Thanks for your reply. Unfortunately, there are more. Please see attached screenshot which shows compare of WPF.NoXaml\Dev directories from public Q2 with latest public of Q3. I use the batch scripts, not the solution files.

I have just started using Binaries\WPF directory for testing this build in my products, since it seems to have the correct files--hopefully that will not be a problem? Of course I won't release the new versions to public consumers until I hear back from you for sure.

Martin

If most Telerik dlls are missing after starting the .bat file probably something went wrong. In the common case this is because the source code is downloaded in a directory which path is too long. If this is your issue, you can move the folder into a directory with a shorter path and see if the build still fails.

About the document processing dlls, well, since the R3 2016 release we ship them only for .NET40 (which is supported also in .NET45). This is why you won't find any document processing dlls (like Telerik.Windows.Documents.Core) in the WPF45 folder. You can find them in the WPF and WPF40 folders. Note that the WPF40 and WPF45 folders are only temporary working folders, and the dlls that should be used after the build are copied in the WPF folder.

Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.