Support for Visual Studio 2017
Hi,
It took a very long time for Visual Studio 2015 support to be released. I think it ended up being November of 2015. Is it being worked on for Visual Studio 2017? If so, is there an estimated timeline for release?
Anyone?
I would very much like to know about an estimated timeline for this as well.
I concur. Visual Studio 2017 support is highly desirable.
Any news on this?
Does anyone monitor these forums anymore?
We'd also like to see VS 2017 support sooner rather than later.
Since I don't think they check these forums too often, I went ahead and made a feature request for VS 2017 support.
feedback.telerik.com/.../218944-sitefinity-thunder-for-visual-studio-2017Thanks Dylan, I've upvoted. I think it's tragic what's happened with these forums.
Hello,
We posted a discussion in the Google Plus community but feel free to comment in the feedback portal or here. We will gather all of the feedback and keep you updated with our decision.
plus.google.com/.../U8Caa6HGonU
Peter
We need Site infinity updates for 2017.
Any news?
AAARGHHH... missing the plugin for thunder support for older sites
+1
Any news on this?!?!
I still have not seen a reply on any of places I know to look. If they have abandoned this, they should at least give us a heads up as a professional courtesy. Otherwise, an occasional note that they are still working on it would help alleviate the frustration that I know a lot of people are feeling.
I am still trying to upsell this tool (Sitefinity) here at work, but stuff like this is rather poor poor PR and customer support and ends up making it a much harder sell.
The product itself is great, but the communication is anything but.
VS2017 is working fine with Sitefinity, but the problem is the THUNDER connection...
That is used to manage ModuleBuilder Views etc... Really anoying to have VS2015 to be spare upon an old workstation to work on that just to have Thunder available... :(
+1 Brian!!! Couldn't agree more.
This has always been the downfall of Telerik/Progress. Poor after sales service in terms of the failed ecosystem, documentation and communication.
The last comment on this post was made five days ago. Four days ago, Peter Filipov commented on the Google Plus thread that he referenced on June 12th (plus.google.com/.../U8Caa6HGonU). For posterity, the content of that post is as follows:
[quote]I read all your comments and I agree with you that the new version of Thunder should be open source and we will work in that directions if in end provides more value to you.
The good news is that I can share some information with you today - our target is to deliver a new version of Thunder with Sitefinity 11.0 (Mar/Apr 2018). I hope that I will be able to provide more details about what this will look like in the next month or so. I want to assure you that we monitor all communication channels and are working very hard on it.[/quote]
You must be kidding... What is the big difference between VS2015 and VS2017 because it's not working at this moment.. With VS2015 we can connect to SF11 projects without a problem... But in VS2017 we cannot even install the plugin.. This is serious a big issue for us.. We have only licenses for VS2017.. not for VS2015 anymore.. :(