You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visualstudio.extensibility primary goal is about out of process and .Net updated version.
However the in process project version still have all the access to visual studio core services.
The reason, as far as I understand is that is not fully feature. A lot of stuffs are experimental.
I'm newer to c# world and extension but some classes of this framework like the projectItem and all the cool function that hide complexity could be use.
As experiment I made some copy and paste plus some small change and it seems to be feasible.
In my opinion these will help the migration of many already existing extensions.
What do you think about?
Am I missing something about the compatibility?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Visualstudio.extensibility primary goal is about out of process and .Net updated version.
However the in process project version still have all the access to visual studio core services.
The reason, as far as I understand is that is not fully feature. A lot of stuffs are experimental.
I'm newer to c# world and extension but some classes of this framework like the projectItem and all the cool function that hide complexity could be use.
As experiment I made some copy and paste plus some small change and it seems to be feasible.
In my opinion these will help the migration of many already existing extensions.
What do you think about?
Am I missing something about the compatibility?
Thank you all in advance
Beta Was this translation helpful? Give feedback.
All reactions