I found this free online training for the VS 2010. Here is the link.
http://launchoffer.appdev.com/
I recommend you check this out…
Check it out. I have a yearly membership with them and the training are pretty good.
Namaskara,
Harsha
I found this free online training for the VS 2010. Here is the link.
http://launchoffer.appdev.com/
I recommend you check this out…
Check it out. I have a yearly membership with them and the training are pretty good.
Namaskara,
Harsha
I am working on implementing an interface that is not finalized yet. Lot of things are in flux. But I want to continue to implement and make changes later on as things progress. The main problem for me right now is not the code but StyleCop. It keeps complaining about lack of documentation in my code. But I don’t want to write the documentation just yet as things can change too much and fix them all later. And, my build is failing. Not a pretty sight.
So in order to overcome this issue, I wanted to disable the StyleCop only for my CS file but leave it working for other files.
The easy way to do this is to put the following lines at the top of the file.
//------------------------------------------------------------------------------
// <auto-generated>
// This code was generated by a tool.
// </auto-generated>
//------------------------------------------------------------------------------
StyleCop does not complain anymore and my build is successful.
Cool, huh?
Later on I can go back and fix those documentation.
Namaskara,
Harsha
Let’s say you have a query like the following
select * from product where lower(name) like 'computer%'
If you want to do the same thing in the Linq to Entities query, it is little tricky (at least for me :))
There is no operator by name 'like’ so we will have to make use of Contains, StartsWith, EndsWith keywords.
Here is goes…
public List<Product> GetProductsByName(string productName)
{
var productQuery = context.Products.Where(p => p.Name.ToLower().StartsWith(productName));
return productQuery.ToList();
}
Namaskara,
Harsha
I have started to code in Visual Studio 2010 BETA 2 and I have some unit tests that are already written up. I wanted to turn on the code coverage. It took a while to figure this out.
First thing I noticed when I double clicked on the Local.testsettings file is that the interface has changed and there are more options than I am used to.
After pocking around for sometime, I discovered that there was a Code coverage check box that I could check.
But even then I could not get the tests to capture the code coverage.
After more pocking :), I found that by double clicking on the Code coverage line in the “Data and Diagnostics” side tab, it opens up the Code Coverage Details window that lets you select the assemblies you want to include for code coverage.
Once I selected my assemblies, I was able to capture the code coverage matrix.
Namaskara,
Harsha
With the availability of Visual Studio 2010 BETA 2 for developing production code, we can finally say Goodbye to Entity Framework 3.5.
I was/am very new to the ORM arena. I spent like 2 months on and off to do some work with EF and to develop some applications and I have had some good and frustrating experiences with this. I wanted to put together some of these here.
In spite of all these advantages, I did suffer from some issues in adopting this effectively in my application development.
Most frustrating factor of all is that I could not settle down with one good code architecture. I considered various levels of separation between the business code and the entity framework code and each one showed its own ugly face.
These kinds of concerns have already made it to the list on the Vote of No Confidence. Take a look at this list.
We now have a new version of Entity Framework in .Net 4.0 which is going to address my concerns and I am now trying to give it a spin and I like whatever I have seen so far. It has POCO support and was developed with testability in mind. I will write up more on the new version later on.
With the availability of this version, I can safely say goodbye to Entity Framework 3.5 and say hello to 4.0.
Here are the great blogs that have helped me to get answers I needed on all of these
Namaskara,
Harsha
Finally found it. I was searching for a blogging tool so that I can install on my machine. Also, I wanted to save them blogs as drafts before I wanted to publish. Writing the blogs online on the blogger.com was an option but it is not elegant as I wanted my tool to be.
After Googling sometime, I discovered the Windows Live Writer. What a relief, this is so good.
This tool offers a familiar writing surface, built-in spelling checker, nice formatting tools.
We can use this tool to blog against many of the well known blogging sites like blogger, WordPress, TypePad, Windows Live Space or your office Sharepoint blogs.
As you are creating the blogs, you can save them as drafts online or on your machine.
The most useful feature of all that I found most interesting are the tabs are the bottom. Edit, Preview and Source. We can preview how our blog is going to look like before publishing that gives a opportunity to make changes.
The HTML generated for the blogs is very clean.
Try it out.
Namaskara,
Harsha