Should an Excel 2010 addin project work in Excel 2013?
The reason I ask is because I created a project in Visual Studio 2010 for an Excel add-in which works fine in Excel 2010 but there are a lot of weird little bugs when it runs in Excel 2013. For example a sheet change event fires twice in Excel 2013 (it correctly fires once in Excel 2010).
Before I go down the route of re-building this project using the Excel 2013 addin template in Visual Studio I wanted to check if anyone else has come across this behaviour?
Related
I have installed Visual Studio 2019 to do some testing on our code base ready for migrating from Visual Studio 2017, I am also testing to ensure it plays nicely with our TFS system (currently TFS 2018 on premises).
It looks as though the Visual Studio Work Item Form is back! (VS 2017 dropped support for this in favour of opening Work Items in a web browser). I've not managed to find any information on this. I like the fact that we might have the option to work with Work Items in the VS IDE as well as the web browser, however its return introduces a few issues:
We use a custom MultiValue control that does have support for the VS 2019 Team Explorer (it last worked in VS 2015). Do you know where I can get hold of a MultiValue control that will work on the Work Item form in the VS 2019 Team Explorer?
Given that the MultiValue control isn't working I would like to continue working with Work Items in a browser. The VS 2019 Team Explorer seems to favour opening Work Items within the IDE, how can I open them in a browser from within the VS 2019 Team Explorer? Better still, how can I configure it to open in a browser by default?
Is there a better place for me to ask these questions?
Work Items should default to opening in the web in Visual Studio 2019. That behavior has not changed from Visual Studio 2017.
There is an option under "Tools->Options->Work Items" to enable the "Legacy experience (compatibility mode)". It sounds like that option has somehow gotten enabled in your installation. If you switch that back to "Default experience", work items should open in the web.
Hope this helps.
Sorry for the inconvenience. This is a designed behavior right now.
Please take a look at this similar issue: TFS work items opened inside Visual Study no longer open in the web browser, they always open in the Visual Studio editor
According to the response from MSFT:
We have re-design the default landing page for work items in Visual
Studio 2019 which only works with server >= 2019. If server is <
2019, work items will be open in Visual Studio only.
Since you are using TFS 2018 with VS2019, you may have to open work item in web portal from browser directly right now. Otherwise, you have to upgrade your TFS version from 2018 to Azure DevOps 2019, if you insist on opening the work item in Visual Studio.
I have installed all packages of Web Essentials 2017, but the add-in that usually is shown on browser is not visible, although I'm pressing Ctrl. It's a problem because I use inspect option a lot.
It is working on Visual Studio 2015.
Thanks for your help
I'm just getting started in Visual Studio 2010 and I'm coming from Delphi 7.
In Visual Studio 2010, what is the equivalent to Delphi's Object TreeView?
Or to ask it another way, in Visual Studio 2010, during WinForm Gui development, how do you navigate your Gui hierarchically? If I have, say, a bunch of Panels with some of them inside of others and some Docked to Client, how can I directly select a specific Panel?
There's something similar called Document outline, you can get it from
View Menu > Other Windows > Document Outline
I have created a Visual web part for SP2010 site, What I need is to implement it into MOSS 2007 site.
Does MOSS2007 support visual web part,and how to do this?
I dont see VS 2010 Support Visual WebPart for 2007, but still you can develop a web part using 2010 (not using any of 2010 Feature) and after you completed the development you can package it manually to be deployed to 2007. Yeah its a extra step. Or you can see how smartpart works. Smartpart is nothing but similar concept in 2007 World.
i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.