Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Extension "Progress Telerik UI for WPF Extension" causes MSBuild properties to be *undefined* #80

Closed
Rand-Random opened this issue Mar 2, 2024 · 3 comments · Fixed by #81
Closed

Extension "Progress Telerik UI for WPF Extension" causes MSBuild properties to be *undefined* #80

Rand-Random opened this issue Mar 2, 2024 · 3 comments · Fixed by #81
Labels
bug

Comments

@Rand-Random
Copy link

When I have the extension Progress Telerik UI for WPF Extension ( https://marketplace.visualstudio.com/items?itemName=TelerikInc.TelerikWPFVSExtensions ) enabled, the MSBuild Properties are undefined.

Here a screenshot of the issue:

image

Thanks in advance, for taking your time.
@Rand-Random Rand-Random changed the title Extension "Progress Telerik UI for WPF Extension" causes MSBuild propertiers to be *undefined* Extension "Progress Telerik UI for WPF Extension" causes MSBuild properties to be *undefined* Mar 2, 2024
@3F 3F mentioned this issue May 3, 2024
Merged
@3F
Copy link
Owner

3F commented May 3, 2024

Hello,

I have prepared a patch, #81. Tested on VS 17.9.6 and installed Telerik.Windows.WPF.VSPackage.X64.vsix
To be sure, please check these artifacts before merging.

@3F 3F added the bug label May 3, 2024
@Rand-Random
Copy link
Author

@3F
Sorry about my late reply.
Got the message during my holiday and it totally slipped my mind. Sorry.

Can happily report it works like a charm. Thanks.

image
image

@3F
Copy link
Owner

3F commented May 16, 2024

@Rand-Random No problem. Thank you for your feedback!

Please note this is not a public release yet.
I'll try to prepare 1.16.1 this week. For #81 and other minor fixes and changes as it was mentioned earlier at https://mastodon.social/@github3F/112385246699027883

3F added a commit that referenced this issue May 22, 2024
@3F
vsSolutionBuildEvent 1.16.1 Public release
fe64f7e 
* FIXED: An *undefined* MSBuild properties (e.g. SolutionDir, SolutionName, SolutionPath, ...)
         when environment is not completely ready. Caused by, for example, third-party plugins like Telerik etc.
         Issue #80.

* FIXED: Broken caching for C# Mode since 1.16. +GenerateInMemory=true support.

* FIXED: UI. Incorrect panel toggling in the main window.

* FIXED: UI. Incorrect display of the scrollbar in the main editor when other actions are activated.

* CHANGED: ISolutionEvent.Enabled option is no longer considered when executed from a script mode.
           For example,
           ```
           #[Core events.Post.item("ShaList").run()]
           ```
           run an `ShaList` action like function regardless of its activity state from a specified script.

* CHANGED: VS IDE Error List now redirects to the main window to the specified action if you click it.

* CHANGED: Core. Updated MvsSln 2.7
           https://github.com/3F/MvsSln/releases/tag/2.7

* CHANGED: CIM. Updated hMSBuild 2.4.1
           https://github.com/3F/hMSBuild/releases/tag/2.4.1

           cim.cmd now supports modern keys, like:
           ```
           cim.cmd -cs ~c Debug
           ```

* CHANGED: CI tools.
            * netfx4sdk 1.2 https://github.com/3F/netfx4sdk/releases/tag/1.2
            * GetNuTool 1.9 https://github.com/3F/GetNuTool/releases/tag/1.9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

+Logic to reload project due to possible lag in early VS environment 3F/vsSolutionBuildEvent
2 participants
@3F @Rand-Random