Laurent Kempé

Displaying application version on TeamCity home page

lkempe — Thu, 12 Nov 2009 09:00:06 GMT

I wanted today to display the application version in front of our builds, something I already did on the past but never with the VCS version.

In fact I used the same BUILD_VCS_NUMBER_<simplified VCS root name> that I described here: Build multiple ClickOnce deployment packages using MSBuild and Team City

Go in the General Settings of your build and adapt as following:

When your software is built it will now display the version:

Automating Publish of ClickOnce with TeamCity

lkempe — Wed, 11 Nov 2009 11:24:47 GMT

The other day I published different posts about the way I automated our build process at Innoveo Solutions to generate different ClickOnce setup using TeamCity:

Build multiple ClickOnce deployment packages using MSBuild and Team City
Building ClickOnce with TeamCity
ClickOnce certificate and TeamCity
Build ClickOnce deployment packages using MSBuild and Team City

Yesterday I was asked to solve one minor issue. At ClickOnce publishing time the publish.htm file was not generated so the ClickOnce version number on the web page wasn’t shown. The publish.htm file is a static file on the targeted deploy directory and IIS uses that file. The file contains a hard coded version 2.0.0.x.

So from a user perspective it was difficult to know if there were a new version. So I was asked to show the correct version.

I knew from past research a way to handle this from the following post: How To: Generate publish.htm with MSBuild

But I went to a more pragmatic solution, as I already had the MSBuild Community Tasks.

I made a copy of Publish.htm to Publish.htm.ori on each targeted deploy directory.

Then I modified my MSBuild script to do the following:

Copy Publish.html.ori to Publish.htm
Use FileUpdate of MSBuild Community Tasks to search the 2.0.0.x string and replace it with the version

 <!-- Deploy Click Once-->
<Target Name="DeployClickOnce">
  <Message Text="####### Deploy ClickOnce $(Configuration)|$(Platform)  ---------#" />
  <Exec Command="xcopy /E /Y $(ClickOnceSrc)\*.* $(ClickOnceDestination)" />
  <Copy SourceFiles="$(ClickOnceDestination)\Publish.htm.ori" DestinationFiles="$(ClickOnceDestination)\Publish.htm" />
  <FileUpdate
    Files="$(ClickOnceDestination)\Publish.htm"
    Regex="2.0.0.x"
    ReplacementText="$(FullVersion)" />
</Target>
 

and the FullVersion is defined as this, using TeamCity BUILD_VCS_NUMBER, which is Latest VCS revision:

 <Major>2</Major>
<Minor>0</Minor>
<Build>0</Build>
<Revision>$(BUILD_VCS_NUMBER_app_Trunk)</Revision>
<FullVersion>$(Major).$(Minor).$(Build).$(Revision)</FullVersion>  </PropertyGroup>
 

And now the Publish webpage display the version correctly!

Watch Several TeamCity Servers With Windows Tray Notifier

lkempe — Wed, 04 Nov 2009 19:49:39 GMT

Browsing TeamCity documentation this evening I discovered that it is possible to Watch Several TeamCity Servers With Windows Tray Notifier

TeamCity Tray Notifier is used normally to watch builds and receive notifications from a single TeamCity server.

In situations, when you have more than one TeamCity server, and want to monitor them with Windows Tray Notifier simultaneously, you need to start a separate instance of Tray Notifier for each of the servers from the command line with the /allowMultiple option:
navigate to TeamCity Tray notifier installation folder (by default, it's C:\Program Files\JetBrains\TeamCity and run the command:
JetBrains.TrayNotifier.exe /allowMultiple
Optionally, for each of the Tray Notifier instances you can specify explicitly the URL of the the server to connect to with the /server option. Otherwise, for each further tray notifier instance you will need to log out and change server's URL via UI.
JetBrains.TrayNotifier.exe /allowMultiple /server:http://myTeamCityServer
See also details in the issue tracker.

So now I am able to have two TeamCity Tray notifier open:

What I also like is to be able to start programs by typing the Windows key and then some text, here for example “te”

To achieve this I created three shortcuts with the different servers configuration and then I placed the shortcuts in my folder C:\Users\Laurent\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\StartMenu in which it is indexed.

Nice!

Windows Backup, Xbox 360 media extender and 0x80070002 error

lkempe — Tue, 03 Nov 2009 09:57:20 GMT

Yesterday I bought a new Western Digital external hard drive of 1TB for 109CHF, incredible how cheap it is now.

Then I configured my Windows 7 backup to use this new hard drive, very easy and the backup in less than 2 minutes.

At the end the backup failed because of drive having errors, then after a Error-checking everything was fine.

So I restarted the backup and got again an error:

Backup encountered a problem while backing up file C:\Users\Mcx1-xx-PC\Contacts. Error:(The system cannot find the file specified. (0x80070002))
Backup encountered a problem while backing up file C:\Users\Mcx1-xx-PC\Searches. Error:(The system cannot find the file specified. (0x80070002))
Backup encountered a problem while backing up file C:\Users\Mcx2-xx-PC\Contacts. Error:(The system cannot find the file specified. (0x80070002))
Backup encountered a problem while backing up file C:\Users\Mcx2-xx-PC\Searches. Error:(The system cannot find the file specified. (0x80070002))

Searching on the Internet I found a forum post with the following solution:

This is a known issue with Media center users. For such users, Windows does not create "Contacts" and "Searches" directories which Windows backup expect to be present. As a workaround, please do the following:
1. Launch Change backup settings.
2. Choose the same backup target and proceed to next page.
3. Select "Let me choose".
4. Expand the user Mcx1-NEO node in the treeview. Expand "Additional locations".
5. Exclude the Contacts and Searches directories for the user.
6. Proceed with configuration and save settings.

Restarted backup and now it works!

Build multiple ClickOnce deployment packages using MSBuild and Team City

lkempe — Tue, 03 Nov 2009 08:10:52 GMT

The other day I posted about Build ClickOnce deployment packages using MSBuild and Team City, and there were something that I didn’t liked in my way of doing it.

I have multiple ClickOnce deployment packages created using TeamCity and MSBuild but each ClickOnce packages have their own Application Revision due to the usage of TeamCity BUILD_NUMBER server build property.

So I changed to use TeamCity BUILD_VCS_NUMBER_<simplified VCS root name>

 <!-- ClickOnce getting build number from Team City -->
<ApplicationRevision>$(BUILD_VCS_NUMBER_MyApplication_Trunk)</ApplicationRevision>
 

And now all my ClickOnce packages have the same Application Revision which is better !

Building ClickOnce with TeamCity

lkempe — Mon, 02 Nov 2009 22:52:25 GMT

Migrating our TeamCity server today I got the following error on the new server:

error MSB3147: Could not find required file 'setup.bin' in …

I for sure fixed that on the older server, and the fix was to have the SDK on the build server. The issue is that I don’t want to install Visual Studio to do that, so here is how I achieved it

Copy my whole c:\Program Files\Microsoft SDKs\Windows\v6.0a folder to the server
Created a registry key
Key: HKEY_LOCAL_MACHINE\Software\Microsoft\GenericBootstrapper\3.5\
Value: Path
Type: REG_SZ
Data: C:\Program Files\Microsoft SDKs\Windows\v6.0a\Bootstrapper\

Then the error was gone and I had my build server ready again to build ClickOnce setup.

TeamCity migration tip

lkempe — Mon, 02 Nov 2009 15:39:27 GMT

Today I am migrating a TeamCity installation from an old server to a new server and discovered that it is really easy to do that!

First I fully re-installed TeamCity using the Windows Setup that JetBrains delivered on the new server.

Then I stopped the old and new instances and transferred the folder .BuildServer from the old server to the new server.

Restarted the new instance and got all my settings from the old instance on the new instance (projects, users…)

This saved my day! and lots of work! Thank you JetBrains for this great tool.

Update

If you set on the original server the Server URL, don’t forget to update it to the new Server URL. This can be done through the Administration > Server Configuration page.

ClickOnce certificate and TeamCity

lkempe — Mon, 02 Nov 2009 15:28:56 GMT

To be able to run a build on TeamCity of a Visual Studio solution containing a ClickOnce manifest which needs to be signed, you will need to add the certificate to the Windows account on which TeamCity services runs.

TeamCity run under Local System account per default.

So you need to add the certificate to this account! But how do you do that?

You will need a tool from SysInternals called PsExec, then using PsExec:

> Psexec.exe -i -s cmd.exe

you will have ran a command prompt on your system in the Local System Account (LSA).

Using that new command prompt, cd to the folder containing your certificate and start it

> my_TemporaryKey.pfx

Then you will face the Certificate Import Wizard in which you click Next > Next > Type the password > Next.

Your certificate is installed now for Local System Account (LSA), and your build should work now.

Enjoy!

Build ClickOnce deployment packages using MSBuild and Team City

lkempe — Tue, 27 Oct 2009 11:25:26 GMT

The other day I was requested to automate our build process to issue different ClickOnce setup for the same application. The main difference was some configuration files pointing to different back end web services.

To start I had to create new build configurations on Team City which used the following settings for the Build Runner:

Targets: Rebuild Publish
Configuration: One per build configurations; e.g DeployClickOnce, integrationDeployClickOnce

Then in my Visual Studio 2008 solution I created several Solution configuration reflecting the different configurations that I needed during my deployment, e.g. DeployClickOnce

Then using the project properties from the solution explorer in Visual Studio I had to set all Publish options I was interested in; Publish Location, Installation Folder Url, Install Mode and Settings, Prerequisites…

The issue now is that the Publish Version automatically increment the revision with each publish. But this doesn’t work with our continuous integration server Team City as it would need to checkin the modified file back to subversion. SO a different approach was needed.

The solution I used is to use the Build Number offered by Team City, so I had to modify the MSBuild script to use the the BUILD_NUMBER. To do that, right click in the Solution Explorer on our project and select Edit Project File:

Then you will face the your MSBuild script, and you will have to search for the configuration that we defined some steps before:

 <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'DeployClickOnce|AnyCPU' ">
 

Then before the end of the closing PropertyGroupd tag add the following lines:

   <!-- ClickOnce getting build number from Team City -->
  <ApplicationRevision>$(BUILD_NUMBER)</ApplicationRevision>
  <InstallUrl>http://myserver.com/</InstallUrl>
</PropertyGroup>
 

ApplicationRevision will overwrite the Application revision using the BUILD_NUMBER defined by Team City.

InstallUrl is another configuration that we want to override because we want to create multiple ClickOnce setup installed from different urls. So for DeployClickOnce you will have an InstallURL and for integrationDeployClickOnce you will have another one.

Now we are ready for the final step in which we want to exchange some configuration files related to the different ClickOnce builds and Publish the output to an IIS server so that our testers can access the different ClickOnce package for the different stages.

ClickOnce secure the different files that are created with checksums so that they cannot be mitigated during the installment transfer. So the only option we have to be able to exchange our configuration files is before compilation. So we had a Target to our MSBuild script:

 <Target Name="BeforeCompile">
  <CallTarget Targets="ExchangeDefaultSettings" ContinueOnError="false" />
  <CallTarget Targets="ExchangeAppConfig" ContinueOnError="false" />
</Target>
 

The BeforeCompile target will be called before each build and will exchange our App.config and another settings file containing stage dependant configuration.

Here is the simple target which exchanges the App.config stored in a configs folder:

 <Target Name="ExchangeAppConfig">
  <Message Text="####### CONFIG Exchange $(Configuration)|$(Platform)  ---------#" />
  <Copy Condition=" '$(Configuration)' == 'DeployClickOnce' " 
        SourceFiles="$(SolutionFolder)\Sources\Application\configs\localhost.App.config" 
        DestinationFiles="$(SolutionFolder)\Sources\Application\App.config" 
        ContinueOnError="false" />
  <Copy Condition=" '$(Configuration)' == 'integrationDeployClickOnce' " 
        SourceFiles="$(SolutionFolder)\Sources\Application\configs\integration.App.config" 
        DestinationFiles="$(SolutionFolder)\Sources\Application\App.config" 
        ContinueOnError="false" />
</Target>
 

The ExchangeDefaultSettings Target works the same.

So before any compilation of our solution using the DeployClickOnce, integrationDeployClickOnce solution configuration the App.config and the default settings file are exchanged. So after the compilation they will be correct according to the stage that we target.

The final step is to Publish the ClickOnce package created to the IIS server. As we defined the Targets: Rebuild Publish, there will be a Rebuild and then a Publish phase in our build script. So now we have to take care of the Publish target.

So we add a Target Publish as here:

 <Target Name="Publish">
  <CallTarget Condition=" '$(Configuration)' == 'DeployClickOnce' " 
              Targets="DeployClickOnce" 
              ContinueOnError="false" />
  <CallTarget Condition=" '$(Configuration)' == 'integrationDeployClickOnce' " 
              Targets="DeployClickOnce" 
              ContinueOnError="false" />
</Target>
 

Which just call a Target DeployClickOnce for the configuration we are interested in: DeployClickOnce and integrationDeployClickOnce.

The DeployClickOnce Target is responsible to xcopy the packages created by the Publish Target to the different IIS path used to host our ClickOnce deployment setup:

 <!-- Deploy Click Once-->
<Target Name="DeployClickOnce">
  <Message Text="####### Deploy ClickOnce $(Configuration)|$(Platform)  ---------#" />
  <Exec Command="xcopy /E /Y $(ClickOnceSrc)\*.* $(ClickOnceDestination)" />
</Target>
 

This is achieved by using two variables ClickOnceSrc and ClickOnceDestination which are also defined per solution configuration like the ApplicationUrl and InstallUrl. The destination is a folder on a IIS server which already has a manually customized Publish.htm file.

 <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'DeployClickOnce|AnyCPU' ">
  <ClickOnceSrc>$(TestsFolder)\Output\$(OutputPath)app.publish</ClickOnceSrc>
  <ClickOnceDestination>E:\Inetpub\Application</ClickOnceDestination>
 

And

 <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'integrationDeployClickOnce|AnyCPU' ">
  <ClickOnceSrc>$(TestsFolder)\Output\$(OutputPath)app.publish</ClickOnceSrc>
  <ClickOnceDestination>E:\Inetpub\Application\integration</ClickOnceDestination>
 

Now you have two build configurations which output two valid ClickOnce setup packages using different stage dependant configurations that your tester can install directly from your ClickOnce web site. And if you have configured the automatic update of the application through the ClickOnce Application Updates then the applciation will be updated automatically when a tester start you application.

Enjoy!

Daily stand up meeting using Skype

lkempe — Tue, 20 Oct 2009 08:48:37 GMT

Today at Innoveo Solutions we had our daily Stand Up meeting using Skype as I am at home. It worked really good ! I can’t wait to experience it on the new plasma TV that we have in our meeting room!

And a Chicken entering the meeting ! Hey Bojan :-)

MVVM Light Toolkit V2

lkempe — Tue, 13 Oct 2009 21:12:53 GMT

At Innoveo Solutions we are using .NET and WPF for our Innoveo Skye® Editor application. Skye® Editor is a distribution channel editor targeting business people letting them edit and configure their insurance products.

From the beginning we have adopted the Model-View-ViewModel architecture. Having our solution growing we were facing the issue of having our ViewModels dependency growing too. Some ViewModel became too much dependent of others. This was obvious in our unit tests whose complexity to setup were growing too. It was time to find a solution to decouple the ViewModels.

The solution came out after a discussion with Laurent Bugnion, the famous author of MVVM Light Toolkit. At that time we used the V1 that already helped a lot in this decoupling.

Now with MVVM Light Toolkit V2 it is even better with the new Messenger API. What we also really appreciated in comparison to other frameworks is that it is really light and the ability to open and edit the user interface into Expression Blend.

So Thank you Laurent for this GREAT framework and I looking forward for V3!

I also would like to thank my managers at Innoveo Solutions who understand Open Source and the need to have people contributing to Open Source projects, even during their professional working time. A Win-Win situation and not just a one way benefit as often.

ReSharper 5.0 Overview

lkempe — Mon, 12 Oct 2009 18:29:45 GMT

As part of the Jetbrains Academy I am using/testing ReSharper 5 for around a month now. It is quite stable for a pre-release and I have lots of fun using it, and as always a productivity boost. Some of my preferred features are: External Sources, ASP.NET MVC integration, Solution-Wide Warnings and Suggestions, Upgrade-to-LINQ Actions. Till now I wasn’t able to test the Native NUnit Support, but this is definitely something I will test in the near future.

Jetbrains just posted on their blog ReSharper 5.0 Overview, check it out:

As promised, we’re publishing general ReSharper 5.0 overview, elaborating on its feature set in more detail.

Please keep in mind that this is a preliminary document. The general picture will stay unchanged but local amendments can not be ruled out at this point, and many user interface items will probably change.

Features

External Sources
A solution is not limited to sources included in your projects, but it also contains sources that were used to build your libraries. Some companies publish parts of their sources using the Source Server feature of debug information files (PDB). This is the same technology that Microsoft uses to provide access to source code for parts of .NET Framework. With ReSharper 5, you can now access it as if it were a part of your solution. When no sources are available, ReSharper does a decent job of reconstructing types’ structure from metadata for your browsing pleasure.

Structured Patterns
“I was assigned to new project, and the source code is full of [your favorite code smell here]. Please, make ReSharper analyze and fix it!”. Fortunately, ReSharper 5 can address this demand. You can set up your own code patterns, search for them, replace them, include them into code analysis, and even use quick fixes to replace! Building patterns and enforcing good practices has never been easier. Corporate and team policies, your own frameworks, favorite open source libraries and tools — you can cover them all.

Project Refactorings and Dependencies View
Once you are used to smart, automated refactorings provided by ReSharper, you can’t think of executing them manually anymore. In this release, we extend ReSharper’s coverage to bring you several refactorings for project structure. With ReSharper 5, you can move files and folders between projects, synchronize namespaces to folder structure in any scope as large as solution, safely delete obsolete subsystems without going type by type, and split a file with lots of types created from usages into their own dedicated files in one go. We have also added special project dependencies view to help you track down excessive dependencies between projects and eliminate them. As an early ReSharper 5 user said, “I no longer feel fear to restructure my project. I just go and do it when I feel it is right to do so”.

Call Tracking
Find usages, find usages, find usages. Formerly, attempting to track call sequences in code could end up with lost context, lots of Find Results windows and frustration. With ReSharper 5, you can inspect an entire call sequence in a single window in a simple and straightforward manner. Stuck in unfamiliar code? ReSharper’s code inspecting tools for the rescue!

Value Tracking
Value Tracking provides you with important information about data flow in your program. At any point in your source code, select a variable, parameter, field or property and ask ReSharper to inspect it. You will then see how its value flows through your program, back to its sources or straight to consumers. Wonder how null could be passed to a specific parameter? Track it!

Internationalization
Software localization and globalization has always been a tough and at times unwanted task for developers. ReSharper 5 greatly simplifies the process of working with resources by providing a full stack of features for ResX files and resource usages in C# and VB.NET code, in ASP.NET and XAML markup. Move string to resource, Find usages of resource and other navigation features, refactoring support, inspections and fixes — all ReSharper goodness for your localization pleasure.

Technologies and Languages

Visual Studio 2010
We will publish more information about Visual Studio 2010 support when VS Beta 2 is released. Currently, ReSharper 5 builds support Visual Studio 2005 and Visual Studio 2008.

C# 4 and VB10
New language versions appear at a great speed nowadays, and ReSharper team works hard to support them right when you need them. ReSharper 5 provides beta support for C# 4 and VB10, as Visual Studio 2010 does itself. Variance, dynamic types, named arguments and optional parameters, embedded COM assemblies — all of these features are supported in the new ReSharper. During VS 2010 Beta 2 phase we’re hoping to learn from your experience using these features and improve their support for Visual Studio 2010 release.

ASP.NET
With this new version, ReSharper support for ASP.NET is improved tenfold. In addition to performance and responsiveness improvements, lots of new features for ASP.NET markup files are introduced to make your life easier. Web-specific navigation, master page support, new inspections and syntax highlighting for web files, File Structure and Go to File Member for in-page navigation and overview, live templates for common markup and more!

ASP.NET MVC
ASP.NET MVC deserved our special attention: special syntax highlighting, inspections, navigation to and from action or controller, and even actions to create new types and methods from usage in pages.

Productivity

IntelliSense
ReSharper continues to bring first-class IntelliSense experience, and the new version gives even more. We have added automatic completion for enum members and boolean values, made automatic triggering smarter, and greatly improved speed. Completion for unresolved symbols in local scope is a new ReSharper IntelliSense feature. Another improvement is completion for all-lower text with CamelHumps — to make cocopro match CodeCompletionProvider — and that means you don’t need to press Shift too often.

Bookmarks
This is a simple yet powerful feature: drop a numbered marker with a single shortcut, jump back at any time with another keyboard key. Up to 10 numbered bookmarks, unlimited unnumbered bookmarks, full list of bookmarked positions in a single pop-up window — all to help you switch between several code spots instantly.

Inspections

Solution-Wide Warnings and Suggestions
We have received a lot of positive feedback from our users regarding solution-wide error analysis that allows you to immediately see compilation errors in whole solution. In ReSharper 5, we took this technology to a new level by adding warnings and suggestions to the list. Now you can browse code smells that ReSharper finds across your solution and quickly improve quality of your code.

Upgrade-to-LINQ Actions
With C# 3.0 and LINQ, developers are able to write data-intensive code more easily by directly describing their intent to the compiler. However, years of imperative programming left us with tons of foreach-style code waiting to be upgraded. ReSharper 5 detects parts of your code that can be rewritten using the new LINQ syntax and suggests to make the conversion automatically, to make the developer’s intent crystal clear.

Use IEnumerable Where Possible
With the power of LINQ, IEnumerable is more than enough to pass a collection of values. So why restrict yourself with API requiring you to pass old-school arrays, Lists and ArrayLists? ReSharper will scan your code base to detect methods that can safely return and accept IEnumerable instead of a more specific type. Of course, we will also take care of the conversion.

New and Improved Code Inspections
We have collected rich customer feedback and went through a list of common errors that developers make in code. Based on that, we have added a ton of highly intelligent inspections to immediately boost your .NET expertise. For example, if you take your API seriously and want it to be well documented, ReSharper will help you by highlighting errors in XML comments.

Other improvements

Native NUnit Support
ReSharper 5 introduces a completely new approach to running your NUnit tests. Our engine is now based on native NUnit code. What it means to you is 100% compatibility with the latest released version of NUnit and full support of its recent unit testing features.

XML Formatting
XML data is an important part of modern applications and you want it to be in order. The new version of ReSharper is supplied with superb configurable formatter for XML files.

Unit Tests without leaving the keyboard

lkempe — Thu, 08 Oct 2009 07:24:54 GMT

I like the Roy Osherove blog: Five Whys, Leadership in software teams.

Follow up on those two posts “How to measure programmer productivity using TDD Katas” or “Be Productive and Go Mouseless”. I would like to share a little keyboard shortcut which save me quite some time on my daily developments.

As you might know I am a fan of ReSharper and when I am doing Test Driven Development I hate having to switch from keyboard to mouse to run the test I just wrote. So searching for ReSharper Keyboard command I found Resharper_UnitTest_ContextRun which I assign to the Ctrl+Shift+<.

Now I can run the unit test I just wrote with just a combination of keys which are really near to each other so really easy!

The bonus of this command is that if I have the cursor in one unit test in a TestFixture class then it will run that particular test, but if I have the cursor out of any unit test method it will run all tests of that TextFixture. Very efficient!

Enjoy it!

Build your .NET project with a right click in Windows Explorer

lkempe — Fri, 11 Sep 2009 06:01:01 GMT

This is a tool that I always install on my machine because it saves you from opening Visual Studio when you just want to compile a solution/project. You can just do it right from the Windows Explorer. Today I spent 10 minutes searching for it, as I couldn’t remember the name, I made a little ‘note to self’.

MSBuildShellExtension lets you build .NET projects without ever opening Visual Studio or the command prompt. MSBuild targets can be executed from your favourite file system tool like Windows Explorer or Total Commander. The possibility to extend MSBuildShellExtension with your own targets and editors, makes it a very flexible and useful tool for all .NET developers.

Devices and Printers empty on Windows 7

lkempe — Sun, 06 Sep 2009 12:16:31 GMT

For some days I had the following issue on my Windows 7 installation: clicking on the start orb then on Devices and Printers would open the window, show a progress bar and then nothing else, a completely empty folder.

I tried a restore that didn’t solved the issue but it reminded me that I installed some days ago a Bluetooth software for a Bluetooth headset I received as a Microsoft MVP gift. This gave me the direction to search for.

I ended up seeing in the Services that the “Bluetooth Support Service” was stopped and that it Statup type was set to disabled. Re-enabling it fixed my issue and now I have again the full list of Devices and Printers shown in the dialog.