Thanks for the elaborate answer.
I still don;t feel very confident about understanding the use of shared libraries, but you have given me some things to look at this evening.

I think it would be very helpfull to add a tutorial to your site (based on the latest available version of VS and the VM exgtension) on how to start a a user-defined library and how to use it in a user project with Visual studio, especially when you don't store everything in the fixed folders or folder structure that Arduino is making you use. 

I've noticed on more than one occasion that Arduino has more than a few quirks if you want to structure your own projects in a different way. Its not very flexible about that

Tim,

I'm still not able to get this thing working ...
As I understand from your answers, the location of the library, sketchbook settings in Arduino or VS should not matter anymore. Is this correct?

On the Blog-page  about Cross-platform library devleopment, you write "Visual Micro also provides a simple way to create a shared project for an existing Arduino library."

How is this done?

Can you please provide me with a sample solution file containing a Arduino project and a shared local Arduino library from which the debugging into the library is working? I'm really missing a step by step instruction on how to create such a thing and get it working

What makes user installed libraries appear in the User combobox control, because my framework is not showing there?
Where do they have to reside, and are there any special file requirements?

I tried the other approach to create a shared project mentioned in your blog to use File>New>Project>C++>Misc>Shared Project to create a empty shared project but the option Misc is not available in the new project dialog.

I'm real sorry to bother you with all this .. does not make me feel very competent to be honest 
I really appreciate the effort you take to get me past this initial learning curve ...

Edit:

Ok, I found how to get the library to appear in the combobox:
placed it in a folder named libraries under the sketchfolder settings, and added a library.properties file
Added the library with the Add User lib, and added a reference to it

Now when I build my solution, all functions from the library are defined twice, the linker doesnt like that
Full build log in attachment....
Quote:

(Not a very helpfull error message from VS btw ... would expect at least  enough info to determine the difference between the two DHT11TemperatureSensor.cpp.o files.

Looking at the build folder, I actually do see the DHT11TemperatureSensor.cpp.o file twice with the same timestamp, in the build folder ("..../debug") and in a folder .../debug/SenseFramework. Looks like the file is compiled for the master project once and for the referenced library another time

Ok, I got a sample project working and my own project almost ..... I think I've got the hang of it now.

What remains is a linking error:
Quote:


I send you a mail with rar and complete build  log.. would really appreciate if you could take a look at that

Tim@Visual Micro wrote on Feb 24^th, 2017 at 8:58pm:

What do you mean by "header files of an #if condition" ?"

[Edit]
I added .cpp files for every .h file that didnt have one already, just including the .h file .. but same result. Linker is stil unhappy with something in wiring.c which is part of the Arduino libs

[Edit2]
I've read up on #pragma once .. it should replace the #ifndef guards if I understand correctly
Tried it, but getting loads of :"error: redefinition of ..."  messages

Thanks for the update. 

Yes, it's always been the case for Visual Micro because it was always the case for arduino until quite recently that adding a project_name.cpp to the project would override all .ino files.

I think it needs to become optional by the sounds of it.

It's quite a useful feature, some people like to ditch the .ino system and a project_name.cpp overrides all the .ino code. Not so useful for others

Thanks. Yes it needs some thought. 

A lot of users know it's the way to override all the .ino files and is a useful feature especially in atmel studio with hardware debugging.

In fact if the project is configured for hardware debug there are messages that suggest creating a project_name.cpp containing the .ino code along with link to an example combined .cpp source file. So that's the opposite message to the one that you need.

Some easy things just don't want to be easy

I think we need a menu item (checkbox switch) that says what it does.