VS 2015: Xaml IntelliSense not working

50 posts, 0 answers
  1. Yehudah
    Yehudah avatar
    20 posts
    Member since:
    Feb 2014

    Posted 30 Jul 2015 Link to this post

    Hi guys!

    I installed the new Visual Studio 2015, and created a new Telerik WPF project with reference to Telerik.Windows.Controls, Telerik.Windows.Controls.GridView, Telerik.Windows.Controls.Navaigation etc.

    I'm using implicit styles.

    Now I want add some Telerik control, but the IntelliSense is not working!

    <Window x:Class="TestWithNavigation.MainWindow"
                    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
                    xmlns:telerik="http://schemas.telerik.com/2008/xaml/presentation"
                    Title="MainWindow" Height="350" Width="525">
            <Grid>
                    <telerik:        ***** The IntelliSense NOT WORKING ********
            </Grid>
    </Window>
     

    If I drop the reference to Telerik.Windows.Controls.Navigation, it's working well.

    Is it a bug? is there a way to resolve it?

    Thanks , Yehudah

  2. Rosi
    Admin
    Rosi avatar
    2528 posts

    Posted 31 Jul 2015 Link to this post

    Hello,

    Thank you for writing us.

    We are aware form this issue and are currently investigate it. We will write back in this thread when the fix is ready.

    Regards,
    Rosi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. Yehudah
    Yehudah avatar
    20 posts
    Member since:
    Feb 2014

    Posted 31 Jul 2015 in reply to Rosi Link to this post

    Hi Rosi, thank you for your response.

    It seems that, unfortunately, Telerik products are not prepare properly for VS 2015. Also Telerik DataAccess is not working.
    All .NET programmers are happy and enjoy the new version, only Telerik programmers still stuck. So for what Microsoft released preview versions?!  RC was released three months ago!

     

    The question is whether you give the Fix to all your customers, or I'll have to buy a subscription for it. My subscription has expired a month ago, and I asked specifically the Telerik support about compatibility to VS 2015, and replied as follows: "thought we don’t officially support VS 2015, there shouldn’t be any issues especially with the Q2 version of our software, which was just released".

    So, I did not renew the subscription, and now I'm afraid I'll have to pay hundreds of dollars just because someone fell asleep and not get ready in time.

  4. Rosi
    Admin
    Rosi avatar
    2528 posts

    Posted 03 Aug 2015 Link to this post

    Hello Yehudah,

    I understand your frustration and concerns.

    However as the fix will be available in one of our next internal builds Sales team will contact you with a offer how to access future versions .Meanwhile you can follow the status of the item here.

    Regards,
    Rosi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  5. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 20 Aug 2015 Link to this post

    I also have this problem. I have to close Visual Studio, kill the VSHub.exe, and restart to reliably get it back. However, it's short lived. Not good.
  6. Rosi
    Admin
    Rosi avatar
    2528 posts

    Posted 21 Aug 2015 Link to this post

    Hello,


    This problem is already fixed and the fix is available with our LIB since version 2015.2.0810. .

    Also you may try removing the design assemblies from the project. This should fix the problem too.


    Regards,
    Rosi
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  7. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 21 Aug 2015 in reply to Rosi Link to this post

    LIB? The Telerik Control Panel indicates 2015.2.728 as the latest -- no upgrade option available.
  8. Dimitrina
    Admin
    Dimitrina avatar
    3769 posts

    Posted 24 Aug 2015 Link to this post

    Hi,

    As it turns out currently it is not be possible to download and install the LIB through the ControlPanel. 

    You can go through the documentation on Using the Hotfix (DLLs Only) and also this help article on how to upgrade with the help with the Visual Studio Extensions.

    Regards,
    Dimitrina
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  9. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 26 Aug 2015 in reply to Dimitrina Link to this post

    FYI -- I'm running the hot fix. I still get the problem where Intellisense disappears when I use Telerik controls.
  10. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 26 Aug 2015 in reply to Anthony Link to this post

    One thing that is different is that building the project will fix the problem now.

    The problem occurs in every project where I use Telerik controls and more specifically when I open or close a tag for a Telerik control. I don't see the problem for any other controls.

  11. Dimitrina
    Admin
    Dimitrina avatar
    3769 posts

    Posted 27 Aug 2015 Link to this post

    Hello,

    Would you confirm you use LIB version 2015.2.0810 or later? Also, would you try the following:
    - Close Visual Studio
    - Clean and Rebuild the solution after removing bin/obj.

    In case this has no effect, then would you please try removing the design assemblies? 

    Regards,
    Dimitrina
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  12. Yehudah
    Yehudah avatar
    20 posts
    Member since:
    Feb 2014

    Posted 27 Aug 2015 in reply to Dimitrina Link to this post

    Bottom line, Dimitrina, internal builds is not the best and perfect solution.

    I suppose that 2015.Q3 edition will be fully compatible with VS2015 & Roslyn, but my subscription has already expired. Will you plan to release SP2 to provide full and complete compliance with VS2015?

    Renewals team offered me to renew my subscription, but I wait to see the commitment of Telerik offer a solution to customers. Because what I earn if I renew my subscription, and after a year I will find out that I have no compatibility with VS2016?

     
     
  13. Petya
    Admin
    Petya avatar
    983 posts

    Posted 31 Aug 2015 Link to this post

    Hello Yehudah,

    This particular issue is going to be resolved with Q3 2015 and so far we haven't identified any other problems with the WPF controls specific to Visual Studio 2015 and Roslyn.

    I can certainly understand your dissatisfaction with this issue, but I'm afraid we're not planning on releasing another service pack version. The next official release is scheduled for the end of September and the preliminary tasks for it have already started, so the time-frame doesn't allow us to ship another version prior Q3 2015.

    At this point, the alternative to using the LIB is to delete the design assembly related to Telerik.Windows.Controls.Navigation from your local installation. It should be located at ..\Telerik UI for WPF 2015.Q2\WPF\Binaries\WPF40\design\Telerik.Windows.Controls.Navigation.VisualStudio.Design.4.0. This would stop the design-time support for the controls located in the navigation assembly, but should allow IntelliSense to work properly.

    Finally, I couldn't engage that future versions of the suite will not have any flaws, but as usually we are committed to deliver solutions that will help our customers in their development process. We're doing our best to prevent such issues in the future and, as in this case, will resolve any blocking problems as soon as they are identified.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  14. Markus
    Markus avatar
    3 posts
    Member since:
    May 2011

    Posted 14 Sep 2015 Link to this post

    Hi there,

    I have the same Problem with a Silverlight Project.

    I have no IntelliSense for XAML and I can't see the Telerik Controls in my Codebehind. When I enter something it works but I have no support of IntelliSense or something else.
    I already downloaded the Hotfix 2015.2.907.1050 and removed all references, added the new one. Rebuild the application.
    No success.

    Do you have any ideas?

     

    Thanks

    Markus

  15. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 16 Sep 2015 in reply to Yehudah Link to this post

    Yehudah said:

    "thought we don’t officially support VS 2015, there shouldn’t be any issues especially with the Q2 version of our software, which was just released".

    So, I did not renew the subscription, and now I'm afraid I'll have to pay hundreds of dollars just because someone fell asleep and not get ready in time.

    Telerik told you that it was not officially supported but that it "shouldn't be" any problems.  That's no guarantee.  YOU made the business decision to accept that risk and also choose not to renew your subscription.  That is on you, not Telerik.  I have had nothing but superior support and interaction with Telerik and recommend them without reservation.

    Why would you expect to receive an update when you have no support contract?  You are not entitled to the update because you didn't pay for it.  Your subscription expired before an officially supported version was released.  Now, ​if you started communicating a little more professionally and with a little bit of respect you may find that they make you some kind of a deal.  Their support is unparalleled in my not-so-humble opinion.  

     

  16. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 16 Sep 2015 in reply to Yehudah Link to this post

    Yehudah said:

    Bottom line, Dimitrina, internal builds is not the best and perfect solution.

    I suppose that 2015.Q3 edition will be fully compatible with VS2015 & Roslyn, but my subscription has already expired. Will you plan to release SP2 to provide full and complete compliance with VS2015? 

    Renewals team offered me to renew my subscription, but I wait to see the commitment of Telerik offer a solution to customers. Because what I earn if I renew my subscription, and after a year I will find out that I have no compatibility with VS2016?

     
     

    An internal build allows people to get on with their development while a fully QA'd version is in the works.   I'm again not sure why you are looking for a service pack to enable an unsupported scenario.  As to your concerns about the future releases, that is again a business decision you need to make.  Personally, I've had years of excellent experience with Telerik.  I only just discovered this issue in the last couple of days and then came here to find a hot fix is already available.  Now that's service!

     

  17. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 16 Sep 2015 in reply to Petya Link to this post

    Petya said:Hello Yehudah,

    This particular issue is going to be resolved with Q3 2015 and so far we haven't identified any other problems with the WPF controls specific to Visual Studio 2015 and Roslyn.

    I just applied hotfix 2015.2.914 and it fixed my intellisense problem as well as another issue that was causing the designer to crash in VS2015 where it worked fine in vs 2013.  I am very happy with this and look forward to the official Q3 release!

    Thanks!

    Dave

     

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  18. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 16 Sep 2015 in reply to David Totzke Link to this post

    To be clear, the hotfix is NOT fixing everyone's Intellisense problem. The problem is still there for me and is as frustrating as ever. My understanding is that it'll be fixed in the Q3 release. If not, I'll be opening up a support incident and I will escalate it further if necessary.
  19. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 16 Sep 2015 in reply to Anthony Link to this post

    Hi Anthony, sorry to hear that.  I'll state some obvious things that I ran into and did and maybe one of them will help you out assuming you haven't done them already.

    • I just ran into this issue today so I used the most recent hotfix build 2015.2.914 so if you haven't given that one a try it might be worth it.
    • I had one project in my solution that was referencing the same libraries but in a different folder and they got missed when I applied the upgrade using the extension wizard - I had to fix that project manually as it didn't show up in the list in the wizard; after fixing it, it's now there with everything else
    • physically delete your bin and obj folders for all projects, especially the obj folder - that has cured many a hair-pulling "why doesn't it just work!!" issues for me.  VS clean never really cleans up everything.
    • I would recommend that you submit your support ticket right now rather than wait so it gets the issue into the pipeline.  The bug for this is marked as complete in the tracking system link provided above so it looks like Telerik believe this issue to be resolved.  By submitting your ticket now, you can make them aware of the issue and perhaps the Q3 release gets an immediate hotfix right after it ships.  Couldn't hurt.

    Anyhow, hope that helps. 

    Cheers,

    Dave

     

  20. Petya
    Admin
    Petya avatar
    983 posts

    Posted 17 Sep 2015 Link to this post

    Hello everyone,

    @Markus and Anthony I'm sorry to hear you're still experiencing issues with this.

    As Dave mentioned, cleaning and rebuilding the project along with deleting the bin and obj folders should resolve the error in most cases.

    The other thing worth mentioning is that the source of the problematic behaviour is one of the design assemblies shipped with the Telerik UI for WPF suite. Visual Studio resolves those slightly differently so it's possible that for some reason the design assemblies related to the official version are still used in your project. There are several resources online where you could find additional information on the topic if you're interested, for example, this MSDN blog post.

    In short, what you can try is uninstall the official version of the controls from the machine or clean the designer's cache at C:\Users\*UserName*\AppData\Local\Microsoft\VisualStudio\14.0\Designer\ShadowCache.

    Please let me know whether that works for you.

    @Dave thank you for your kind words and your continued trust! We strive to provide our customers with the best possible service and your feedback means a lot to us.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  21. Jonah
    Jonah avatar
    24 posts
    Member since:
    Oct 2012

    Posted 23 Sep 2015 Link to this post

    I tried following the steps in the Hotfix and I am having an issue where the controls all give the error "does not exists in namespace" However I can see the controls with intellisense.
  22. Petya
    Admin
    Petya avatar
    983 posts

    Posted 25 Sep 2015 Link to this post

    Hello Jonah,

    Could you please double-check if all references are resolved from the same location and are from the same version? The most common cause for such error is assembly mismatch.

    You can also try deleting the bin and obj folders manually.

    Please keep me posted about the results.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  23. Yehudah
    Yehudah avatar
    20 posts
    Member since:
    Feb 2014

    Posted 26 Sep 2015 in reply to Petya Link to this post

    Petya said:so far we haven't identified any other problems with the WPF controls specific to Visual Studio 2015 and Roslyn.

     

    May be this:

    http://feedback.telerik.com/Project/143/Feedback/Details/169475-gridviewcolumngroup-crashes-xaml-designer 

     

     
     
  24. Petya
    Admin
    Petya avatar
    983 posts

    Posted 30 Sep 2015 Link to this post

    Hi Yehudah,

    I can see that the team already confirmed this and provided a workaround.

    Like I mentioned before, I can certainly understand your dissatisfaction with the situation, but I'm in no position to guarantee we won't find any other issues in the future as well. This particular problem is rather peculiar as we didn't find any differences in the way the style for the column groups and those for other elements are defined, yet only the column groups cause the design-time issue.

    If you find any other issues please do bring them to our attention and we'll do our best to resolve them.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  25. Vaidas
    Vaidas avatar
    2 posts
    Member since:
    May 2015

    Posted 07 Oct 2015 in reply to Petya Link to this post

    In the Q3 release XAML intellisence stops working after couple of minutes.

    Frequent restarting for VS2015 needed to make it usable

  26. Petya
    Admin
    Petya avatar
    983 posts

    Posted 08 Oct 2015 Link to this post

    Hello Vaidas,

    We tested various setups, but couldn't replicate a case in which IntelliSense stops working with the mentioned release, which leads me to believe the issue might be related to a specific setup. Could you please try isolating this and send us more details on the behaviour, so we can troubleshoot it locally. You can also open a support ticket and attach a sample application where this is reproducible.

    Thank you in advance for your cooperation. We're looking forward to hearing from you.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  27. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 08 Oct 2015 in reply to Petya Link to this post

    Hello Petya,

     I am now experiencing this same problem.  Things were working very well until I upgraded from the most recent hotfix to the Q3 release.  Intellisense now fails almost immediately in VS2015.  There are no errors or exceptions thrown and the designer keeps working but Intellisense just stops.

    If there's any advanced logging I can enable or anything I can do to help track this down I'd be happy to help out.  I'll see what I can do to replicate the problem in a sample project.

    Dave

     

  28. David Totzke
    David Totzke avatar
    13 posts
    Member since:
    Jul 2006

    Posted 08 Oct 2015 in reply to David Totzke Link to this post

    PS - Forgot to mention that I've done everything suggested in the thread above as well as uninstalling all previous versions of the product from my machine.  Only the Q3 Release is installed.

    Cheers,

    Dave

  29. Petya
    Admin
    Petya avatar
    983 posts

    Posted 09 Oct 2015 Link to this post

    Hello Dave,

    As you can see, we already received other similar report, but we're still unable to replicate the issue. Could you share the following information with us:
    - What Telerik assemblies are added to the project?
    - Are you testing this in your project or in a standalone sample? In the former case, would it be possible to try creating a new project to see if the behaviour is the same?
    - Do you have any code productivity tools like JustCode installed?
    - What are the exact steps you're executing? If you can send us a short screencast, that would be great.
     
    We also received a report stating that the issue occurs in a view where only the Telerik namespace is added. The client mentioned that removing the namespace and rebuilding the project brings back IntelliSence. Could you try those steps and let me know the results?

    If you can isolate this in a sample and send it over, that would be ideal. In the meantime, we'll continue trying to reproduce the behaviour.

    Thank you in advance for any information you can share.

    Regards,
    Petya
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  30. Anthony
    Anthony avatar
    47 posts
    Member since:
    Apr 2012

    Posted 10 Oct 2015 in reply to Petya Link to this post

    This is still a problem for me as well after installing the Q3 version.

     I don't know when I'll be able to dig into it further, but I think it's safe to say it's a more widespread problem.

Back to Top