<p>I am recently in charge of an older app written in <code>C#</code> using <code>asp.net 1.1</code>.  </p>

<ol>
<li>Are there any resources to guide me in converting the application to a newer version of of the <code>.NET Framework</code>. 
<em>My main pause is that there are ton's of customized <code>DataGrids</code> in the app as it is written now and since so much of the code needs to be rewritten to use <code>GridViews</code></em> ...</li>
<li>is it worth trying to convert the grids in the application to use <code>Silverlight</code> in the attempt to move this code into the future.</li>
</ol>

[{'answer_id': 42883, 'author': 'Jason Bunting', 'author_id': 1790, 'author_profile': 'https://Stackoverflow.com/users/1790', 'pm_score': 0, 'selected': False, 'text': "<p>Regarding DataGrids - I don't think you have too much to worry about, DataGrids still work in current versions. It's just that going forward, you should use GridViews.</p>\n\n<p>I am sure there are other things you may want to check into though, deeper framework issues. But I don't know enough about those things to speak to that particular point.</p>\n"}, {'answer_id': 42944, 'author': 'Guy Starbuck', 'author_id': 2194, 'author_profile': 'https://Stackoverflow.com/users/2194', 'pm_score': 2, 'selected': False, 'text': "<p>I had a similar experience, and the only thing that we had to replace was a third-party control that we were using in the 1.1 app, and the vendor had gone out of business an never released a version that worked with  .NET 2.0.  We ended up replacing it fairly easily with an AJAX Control Toolkit control.</p>\n\n<p>Other than that, the compiler does a pretty good job of telling you what to do with respect to deprecated method calls.</p>\n\n<p>I'd suggest making a copy of the code and upgrading the site in Visual Studio and see what happens.  Just open the solution in Visual Studio 2005 or 2008, the IDE will walk you through the upgrade automatically.  Get it to compile, then if you have any documented tests you should run through them.  If not, you'll want to plan testing to make sure all your functionality still works like it did before the upgrade.</p>\n\n<p>Migrating to Silverlight sounds like fun, but if you can get it upgraded and working, I'd probably push that off until a later release -- my experience tells me that you might get into trouble if you bite off too much at once if there is no show-stopping technical reason.</p>\n"}, {'answer_id': 43597, 'author': 'Ian Nelson', 'author_id': 2084, 'author_profile': 'https://Stackoverflow.com/users/2084', 'pm_score': 1, 'selected': False, 'text': '<p>I would suggest that as part of the upgrade you opt to move to a Web Application Project rather than a Web Site Project, as the former is conceptually similar to the VS2003 web project model.</p>\n\n<p>Here\'s a nice short post summarising the differences:</p>\n\n<p><a href="http://maordavid.blogspot.com/2007/06/aspnet-20-web-site-vs-web-application.html" rel="nofollow noreferrer">http://maordavid.blogspot.com/2007/06/aspnet-20-web-site-vs-web-application.html</a></p>\n\n<p>As others have said, don\'t worry too much about the DataGrids, the upgraded site should be backwards-compatible in this respect.</p>\n'}, {'answer_id': 68662, 'author': 'Tim', 'author_id': 10363, 'author_profile': 'https://Stackoverflow.com/users/10363', 'pm_score': 2, 'selected': False, 'text': '<p>This MSDN document may be useful to you as you upgrade your application, it contains lists of breaking changes between 1.1 and 2.0, and work arounds for resolving them:</p>\n\n<p><a href="http://msdn.microsoft.com/en-us/netframework/aa570326.aspx" rel="nofollow noreferrer">Breaking Changes in .NET Framework 2.0</a></p>\n'}]
['https://Stackoverflow.com/questions/42879', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/4491/']