I used my VS2008 reports worked correctly. I migrated to VS2010 and my reports have stopped working.
Earlier I called methods of the TextBox directly from expressions like this:
=First(Fields!CteImpressao.Value.ObterValor("Number"))
or
=First(Code.AtribuirCte(Fields!CteImpressao.Value))
Now in VS2010 it generates #Error
Since the classes marked as serializable.
Microsoft has changed the way the reports are assembled, so you can no longer use the RDLC as was done in version VS2008.
Just generating a data source other way for my report funcionace correctly.
Related
I have a VS2013 solution which includes unit test projects. When I open the solution and rebuild it in VS2015 Enterprise, I get numerous errors of the pattern
CS0246 The type or namespace XXXX_Accessor could not be found
Is this a VS2015 issue? Does VS2015 Enterprise no longer support Accessors? The solution builds perfectly well in VS2013 Pro, and I can't see any missing references in the project References lists in Solution Explorer
TIA
Doh! It turns out that accessors were deprecated in VS2010 (which we skipped when we upgraded from VS2008) but continued to work up to VS2013. In VS2015, which we are now trialling, they don't compile so have to be expunged from the test projects and (this is our way of resolving the subsequent visibility errors) the test code amended to use 'real' classes instead of the accessors and private members accessed by the tests changed to internal. Much simpler than using reflection, as suggested by others who have encountered this problem.
I have a number of extension methods on System.Web.Mvc.HtmlHelper. They all work, the pages load up just fine. No compilation errors nor runtime errors. I am using my own derived view class, derived from System.Web.Mvc.WebViewPage< T >
The issue is intellisense in these views are not showing my extension methods as available. In fact they're not showing anything as available from my derived view class. When I go to definition on the #Html it shows that VS is looking at System.Web.WebPages.HtmlHelper.
Is there a way to correct this and have Visual Studio recognize the base class I'm using? Once again this all builds correctly and runs just fine, everything works as expected.
Additional info while researching this:
It looks like tooling support for VS 2012 and MVC 5 has yet to be released and is currently expected to be released in mid-november. Source. This may indicate the support isn't complete in VS2013 as well.
When you upgrade to MVC5 through Nuget, there are a number of files that need to be edited in order to ensure that your application builds and runs correctly, and has support for the right tooling.
All of this information is captured in this Microsoft guide for upgrading from ASP.NET MVC 4 to ASP.NET MVC 5. Please note that if you read the comments of the guide, there is still an issue with VS2012's tooling due to what VS2012 expects versus the updates to the way the new toolchain attempts to find binaries. A patch is expected for MVC5 support in VS2012 by November 2013.
Hopefully following the steps in the guide help you solve your issue. They worked fine for me. (Note that I started from a base project and attempted to upgrade it in VS2013. I did not start with an existing project.)
We are using WinForms Reoprt viewer control. Everything worked fine until we migrated to VS2010 from VS2008. VS2010 converts our project to corresponding version simultaneously changing the version of Microsoft.ReportViwer.Common and Microsoft.WinForms from 9.0 to 10.0. Also during the first opening of .rdlc file VS2010 suggests to convert it.
After such manipulation report crashes and displays the following error:
"An error occured during local report processing. An error has occured during report processing. The Group expression used in Groping '' returned a data type that is not valid."
However if I change assemblies version back to 9.0 everithing works fine.
Does anybody have any idea or help how to make it work with newer libraries?
I've found the solution. This problem was with nested field attributes and fixed in VS2010 SP1. This article explains this issue http://blogs.msdn.com/b/brianhartman/archive/2010/10/27/nested-objects-in-local-mode.aspx
I'm trying to move my VS 2008 solution to VS 2010. Everything works perfectly (compile and link) if I keep the target framework at 4.0.
When I change the framework 2.0 and change the platform framework v100 (to get past compile errors) only to run into metadata linking errors, like this one:
error LNK2022: metadata operation failed (80131195) : Custom attributes are not consistent: (0x0c0000f7). C:\Development\Main\Filemaster\SoxService\MSVCMRTD.lib(managdeh.obj)
I've read that I'm supposed to use ILDAsm but it doesn't like my obj file and since the link didn't complete I don't have an exe to load.
Can anyone please provide some advice on how to find the sorts of errors?
I hate nothing worse than fighting the tool!
I was able to get around this problem by going into the project XML file itself and changing the TargetFramework to be 4.0 After that everything compiled and linked fine.
Hans he is referring to C++ Native Multi-Targeting which can be found at this location Platform Framework can be changed under project Properties > General and is advised by the article - however this does not work due to apparent bugs in VC++
Duplicate: Why are C# collection-properties not flagged as obsolete when calling properties on them?
I just migrated a .NET 1.1 project to .NET 2.0 using Visual Studio 2008. I know that there are references to obsolete methods in the project.
But Visual Studio does not show "obsolete"-warnings after building. The build succeeds and shows only 3 warnings from members that are assigned a value that is never used. When I remove these members there are no warnings at all.
I NEED THESE "OBSOLETE"-WARNINGS
The Warning level is 4 (maximum), Warnings are enabled.
Just one sample:
protected internal DataConnector()
{
_connectionString = ConfigurationSettings.AppSettings["ProductConnectionString"];
}
All references that should result in an "obsolete"-warning are to members of classes of the .NET Framework.
Is the code calling the obsolete method(s) itself flagged as obsolete?
Just taking a shot in the dark here, but is the usage of an obsolete member taking place in a project that you're REFERENCING, and when you're building it isn't actually rebuilding that project? If that's a possibility, I would try manually building the project where the usage is taking place, or just rebuilding the entire solution.
Make sure you are doing a full build on the project, not just an incremental build.
Jeff Yates is right, this is a duplicate to Why are C# collection-properties not flagged as obsolete when calling properties on them?
It is a bug in the C# 3.5 compiler reported here:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=417159
I checked it: copied the csc.exe commandline from the output window to a cmd-console. When I change the directory to the .NET 2.0 directory (using C# 2.0 compiler), it shows the warnings. Microsoft knows this bug and fixed it in C# 4.0 but will not fix it in the 3.5 version.