A developer asked a question on MSDN that was similar to a question a few days earlier so I decided to help folks get over the problems of setting report parameters in ReportViewer projects.
Recently in SQL Server Category
I’m working the forums this week and I’ve already seen several questions asking if SQL Server Express Edition is up to the task. Shown below are the Microsoft links to Express’ limitations but I would like to clarify just what the mean (and can’t say).
My new webinar/lab class launches next week on February 8-10. It’s the premier edition of a series of lectures and lab exercises that walk report developers through the process of learning enough Visual Basic to create serious report expressions for use with Reporting Services reports.
We follow the introduction to Visual Basic with an in-depth discussion of how to add code-based expressions to your reports, but more importantly, how to share the code between reports. The final session shows how to create managed-code DLLs that can be developed in C#, VB.NET or any .NET CLR language and leveraged by the report processor when rendering your report.
The mentored lab exercises walk you through the process of creating a Visual Basic test-harness, coding and debugging complex code expressions and finally, you’ll create your own sharable managed-code DLL that can be used in all kinds of deployed reports.
Here’s the link to the Progressive site.
This entry focuses on the code developers add to reports make them work, look better or expose custom functionality. Sometimes it’s simply adding green-bar but when these expressions get complex or have to be incorporated in many places in the report or in many reports (or both) productivity suffers.
Just thinking aloud here. So, let’s say you have a team of report developers and you find that more than one report needs to access a common set of routines.
It was brought to my attention that there was some concern that the “amateur” LightSwitch developers would be incapable of writing stored procedures so the tool should not support accessing them—it doesn’t. Here is my response along with a couple of other questions for Microsoft…
Microsoft is gearing up to announce “LightSwitch”, it’s newest data application developer tool. Targeted to developers of “…all skill levels” it’s designed to permit access to local or remote data sources including SQL Server, Azure and SharePoint. I assume this means that amateur developers will have another tool to work with—assuming they can afford it and their IT organization will let them use it.
Frankly, I’ve known about this new offering for some time but until now, I was under NDA and could not reveal any of its details (or even the name). Now that it’s been released, I have a few choice words to add to the drumbeat…