Microsoft Visual Studio Community 2019 Version 16.8.4.
This is a CLR Project (.NET Framework 4.5).
I'm not sure about the origin of this bug, so I cannot fill in a bug report to its respective program.
I either found a bug on Visual Studio Community 2019 or AxWMPLib::AxWindowsMediaPlayer. When adding a custom control derived from AxWMPLib::AxWindowsMediaPlayer in the Designer, if you switch the Language of the form by the Designer then it gets all blank and you are forced to close the Designer. For another custom controls like derived from System::Windows::Forms::* that bug doesn't happen.
This is my ClassLibrary1.dll e.g:
#pragma once
using namespace System;
namespace ClassLibrary1 {
[System::ComponentModel::ToolboxItem(true)]
public ref class MyMediaPlayer : public AxWMPLib::AxWindowsMediaPlayer
{
public:
MyMediaPlayer() {}
};
}
Problem solved on version 16.8.6. So it was actually a Visual Studio bug.
Related
I had visual studio 2019(don't know which version) and intellisense was working fine. It was suggesting every unity functions(like start, update, onTriggerEnter, etc.) as well as user defined functions.
Then there is info that Microsoft has removed its support for this version and i had to update it to 2019 v16.11.18. And now the intellisense which was previously working fine in every respect, stopped suggesting unity event functions or monobehaviour functions only. Other keywords like gameobject, transform, GetComponent or user defined functions are being suggested without any problem. Its just some those crucial monobehaviour functions which got this problem.
I have double checked external tools settings in unity as well as tools for unity option in visual studio. My visual studio is not saying miscellaneous files on top left and i have nothing more to do.
Please help me..
I think it is now fixed. What i did is open visual studio installer and click repair on my visual studio. That's it.
I have the following test code. But cant see the tests in either Test Explorer or Resharper.
What am I missing? I have made the class public, I have tried cleaning the project, i have tried both default architectures in the test settings. I am running Windows 7. xUnit 1.9.2, Resharper 8.1 Full Edition
using Xunit;
namespace MonkeyFace.Specs.Registration
{
public class ValidApplicationReceived
{
[Trait("A valid application is submitted","")]
[Fact(DisplayName= "A user is added to the system")]
public void User_is_Add_To_System()
{
Debug.Print("hi");
Assert.Equal(1,1);
}
Do you have the xunit ReSharper runner extension installed? You need to install it from ReSharper -> Extension Manager.
If it's installed, do you see anything in the editor? Any icons next to the class or method to indicate tests?
I had to install the xUnit.net runner for Visual Studio 2012 and 2013 by using the Tools -> Extensions and Updates menu in Visual Studio
We recently started using Telerik Reporting. Some users use the Telerik Report Designer, while I use Visual Studio 2012. Is there a way to import their trdx reports into my Visual Studio class library?
This is currently not supported and in all honesty would be unnatural and tedious task for Telerik to do if they were to do it (create .net class from xml file). I believe they did it one way(VS -> xml) as in most cases devs would create a base/template report that regular users can modify.
Carry over from social.msdn.microsoft.com...
http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/4993d0bf-94e8-4d14-aff1-3458b4ad467f?prof=required
Original Post
I try to migrate a project from 2010 EF 4.3.1 (modified EntityObject generator template) up to vs 2012 rc, ef 5.0 rc and .Net 45 rc.
Painfully, my old T4 template doesnt work any longer. Where can I get the correct template to migrate it to EF 5.0 ?
I can compile the old project, but after starting the app I receive an exception with "different scheme detected".
My contribution, still unresolved
The EntityObject code generation template was available in VS 11 Beta on a "clean" machine, so I would imagine it's an upgrade issue/conflict, possibly related to having EF 4.2 June 2011 CTP installed prior (despite uninstalling).
VS 2012 Repair - did not fix the problem
VS 2010/2012 RC Uninstall/Reinstall - did not fix the problem
VS 2012 RC install on a clean machine - don't have time atm
Screenshots
What I'm expecting to see when adding a code generation template
What I see when adding a code generation template
Only DbContext in Extension Gallery
We are finishing verifying VSIX versions of the EntityObject and Self-Tracking Entities code-gen templates. These should be available in the Visual Studio Gallery (or the online tab of the "Add code generation item" menu) shortly if verification goes well. I will reply here as soon as they are uploaded.
Sorry for the long wait on these ones. The templates are now available on Visual Studio Gallery. See this page for details - http://msdn.microsoft.com/en-US/data/JJ613116#EntityObject
~Rowan
I wrote my own Debugger Visualizer.
It, and the attributes, are in their own assembly. There is no references or attributes in the assembly containing the class to be debugged - I want to make a drop-in dll that is optional for people to use.
The class I am trying to debug is a generic.
[Serializable]
public class FinCellTable<S> : IFinCellTable, IEnumerable<List<FinCell.IFinCell>>
where S : class, FinCell.IFinHeaderCell, FinCell.IFinCell, new()
Here is the visualizer:
[assembly: System.Diagnostics.DebuggerVisualizer(
typeof(Financials.Debugging.CellTableVisualizer),
typeof(VisualizerObjectSource),
Target = typeof(Financials.Transformation.IFinCellTable),
Description = "FinCell Table Visualizer")]
[assembly: System.Diagnostics.DebuggerVisualizer(
typeof(Financials.Debugging.CellTableVisualizer),
typeof(VisualizerObjectSource),
Target = typeof(Financials.Transformation.FinCellTable<Financials.FinCell.FinHeaderCell>),
Description = "FinCell Table Visualizer")]
namespace Financials.Debugging
{
public class CellTableVisualizer : DialogDebuggerVisualizer
{
protected override void Show(IDialogVisualizerService windowService, IVisualizerObjectProvider objectProvider)
{
if (windowService == null) throw new ArgumentNullException("windowService");
if (objectProvider == null) throw new ArgumentNullException("objectProvider");
var data = (IFinCellTable)objectProvider.GetObject();
using (var displayForm = new CellTableVizForm())
{
displayForm.PopulateForm(data);
windowService.ShowDialog(displayForm);
}
}
}
}
I am running Visual Studio 2010, and the following directory contains the .dll and .pdb of the Visualizer Assembly:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\Visualizers
I place a breakpoint on an instance of IFinCellTable that is specifically FinCellTable. It does not show the magnifying glass.
I debugged Visual Studio using another Visual Studio as the first VS was debugging. I watched the output window as the first VS loaded dll's. When I triggered a visualizer on a datatable, the second VS outputted that it loaded Microsoft.VisualStudio.DebuggerVisualizers.dll and Microsoft.VisualStudio.Debugger.DataSetVisualizer.dll (the latter from the correct directory I said above). (The Modules window behaves/shows the same.)
So obviously my Debugger Visualizer Drop-In assembly is not be loaded by VS, so it doesn't know to show the magnifying glass.
How do you get visual studio to load Visualizers up-front, so drop-in visualizers work and you don't need to edit your original code?
Wild guess: are you sure the correct files are in C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\Visualizers, not in C:\Users\<you>\AppData\Local\VirtualStore\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Packages\Debugger\Visualizers?
If yes, that's due to UAC Virtualization.
This question is over 5 years old, so I assume it's no longer relevant to the original poster, but for anyone else trying to do something similar:
System.Diagnostics.DebuggerVisualizer does not work when target is an interface. You have to specify a concrete type. You have to specify the attribute on every single concrete type you want to visualize:
[System.Diagnostics.DebuggerVisualizer("Financials.Debugging.CellTableVisualizer, Financials.Debugging, Version=1.0.0.0, Culture=neutral, PublicKeyToken=...")]
[Serializable]
public class FinCellTable<S> : IFinCellTable, IEnumerable<List<FinCell.IFinCell>>
where S : class, FinCell.IFinHeaderCell, FinCell.IFinCell, new()
{
I believe this can be disabled in Tools > Options:
If you do not see the effects of DebuggerDisplay or DebuggerTypeProxy ensure that Tools > Options > Debugging > General > Show raw structure of objects in variables windows is NOT checked.
The correct folder to place it is:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Packages\Debugger\Visualizers. Once you place this DLL there and restart visual studio then you should get a "magnifying glass" over "Expression" type of variables (in debugging mode you will get it in watch window and also when you move your mouse cursor over the variable)