3 posts tagged “visual studio 2008”
Everyone who regrets installing Visual Studio 2003 can take pleasure in knowing there is an alternative. There is an MSBuild Extension called ‘MSBee’ that was built to manage building applications using Visual Studio 2005 projects that target .NET 1.1. Moving forward to use Visual Studio 2008, there is an extension to that called CrossCompile.CSharp.targets and CrossCompile.CSharpWeb.targets Referencing article: http://devlicio.us/blogs/ziemowit_skowronski/archive/2008/08/22/working-with-net-1-1-in-visual-studio-2008-and-team-server.aspx From that, it is possible to create a Visual Studio 2008 Project and ensure that it compiles directly to .NET 1.1 Assemblies. Setup: Download MSBee and install it (make sure you install the .NET Framework 1.1 and the .NET Framework 1.1 SDK): http://www.codeplex.com/MSBee Download CrossCompile and export the targets to your %Program Files%\MSBuild directory. http://www.gl-net.org.uk/Files/CrossCompile.zip Take a look at that article on how to take an existing project and ensure that you can convert it for Visual Studio 2008. New Class Library Project Templates Or if you happen to need a new project, I have created a Visual Studio Templates just for that: http://nyxtom.googlepages.com/ClassLibrary-Net.1.1.zip Note about adding additional references: Your project is set to .NET 2.0 so by default it any additional references added are only going to show as 2.0 References. To fix this, (say you add System.Web.Services) unload the project, edit the .csproj file and find the section that indicates a ‘HintPath’. You can either specify the .NET 1.1 Framework HintPath or delete the HintPath altogether. Without the hint paths, Visual Studio will assume .NET 2.0 and thus give you the ability to write 2.0 code; however any 2.0 based code you do write will cause a compiler error as it isn’t supported by the .NET 1.1 CSC ran by CrossCompile and MSBee. Enjoy J
I did a search to do this and the few links that came up happened to not work. However after a few iterations and a few adjustments to the examples I did find, I managed to get it working. Create a text file and copy in the following:
Hey for anyone interested, I have started a Spanish blog at nyxtomes.vox.com. I am trying to master the language so any help would be greatly appreciated.
A few new things from the tools of the trade.
Translating System.Drawing.Bitmap to a WPF BitmapSource
To get the Bitmap you would have to call CopyPixels on the BitmapSource and convert it to a Bitmap-
int width = transformedBitmapSource.PixelWidth;
int height = transformedBitmapSource.PixelHeight;
int stride = width * ((transformedBitmapSource.Format.BitsPerPixel + 7) / 8);
byte[] bits = new byte[height * stride];
transformedBitmapSource.CopyPixels(bits, stride, 0);
unsafe
{
fixed (byte* pBits = bits)
{
IntPtr ptr = new IntPtr(pBits);
System.Drawing.Bitmap bitmap = new System.Drawing.Bitmap(
width,height,stride, System.Drawing.Imaging.PixelFormat.Format32bppPArgb,ptr);
return bitmap;
}
}
To do the reverse:
System.Windows.Media.Imaging.BitmapSource bitmapSource = System.Windows.Interop.Imaging.CreateBitmapSourceFromHBitmap(
bitmap.GetHbitmap(),
IntPtr.Zero,
Int32Rect.Empty,
System.Windows.Media.Imaging.BitmapSizeOptions.FromEmptyOptions());
WPFImage.Source = bitmapSource;
Thanks!
Linq Tutorials
LINQ: .NET Language Integrated Query
By Don Box, Anders Hejlsberg
LINQ to SQL: .NET Language-Integrated Query for Relational Data
By Dinesh Kulkarni, Luca Bolognese, Matt Warren, Anders Hejlsberg, Kit George
.NET Language-Integrated Query for XML Data
By Michael Champion
The .NET Standard Query Operators
By Anders Hejlsberg, Mads Torgersen
By Anders Hejlsberg, Mads Torgersen
Orcas Beta Samples
http://go.microsoft.com/fwlink/?LinkID=85559
(Above link will always point you to the updated sample)
.NET Micro Framework
The Microsoft .NET Micro Framework is an environment that extends the advantages of Microsoft .NET and the toolset in the Microsoft Visual Studio development system into a class of smaller, less expensive, and more resource-constrained devices than previously possible with other Microsoft embedded offerings.
http://msdn2.microsoft.com/en-us/embedded/bb278106.aspx

Acropolis
The Microsoft code name “Acropolis” Community Technology Preview is a set of components and tools that make it easier for developers to build and manage modular, business focused, client .NET applications. Acropolis is part of the “.NET Client Futures” wave of releases, our preview of upcoming technologies for Windows client development.
Acropolis builds on the rich capabilities of Microsoft Windows and the .NET Framework, including Windows Presentation Foundation (WPF), by providing tools and pre-built components that help developers quickly assemble applications from loosely-coupled parts and services. With Acropolis you will be able to:
- Quickly create WPF enabled user experiences for your client applications.
- Build client applications from reusable, connectable, modules that allow you to easily create complex, business-focused applications in less time.
- Integrate and host your modules in applications such as Microsoft Office, or quickly build stand-alone client interfaces.
- Change the look and feel of your application quickly using built-in themes, or custom designs using XAML.
- Add features such as workflow navigation and user-specific views with minimal coding.
- Manage, update, and deploy your application modules quickly and easily.
http://windowsclient.net/Acropolis/Default.aspx
Hasta manaña!