Why not put the DateTime picker in a Panel that's slightly larger and set the color of the panel? That would give you a bit of a border and you could even 'flash' it if you wanted to.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.
I just forwarded the question on to the Blend team for a more official answer. They said they don't have any annoucments to make about future versions or service packs at this time. However, they also went on to say they are committed to enabling existing Blend 2 customers to create Silverlight 2 content when it is released at no charge. So, yes, there should be some sort of free update or add-on for existing Blend 2 users.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.
The Expression team has said that Blend will continue to rev as Silverlight revs. I'm not sure whether there will be a full studio update when Silverlight ships, but I would expect a more finalized release or service pack for Blend at that time. You can view upgrade information here: http://www.microsoft.com/expression/products/Upgrade.aspx[^] Service packs and minor releases are of course free. When Blend went from 1.0 to 2.0 the upgrade cost was $99. You can also buy a subscription for continuous updates. Other ways to get Expression: If you have an MSDN Pro license you have Expression Blend already. If you have an MSDN Pro Premium license you have Expression Studio already. If you are a college student you have access to Expression Studio through DreamSpark: https://downloads.channel8.msdn.com[^] DreamSpark is currently only available in the United States, the United Kingdom, Canada, China, Germany, France, Finland, Spain, Sweden, Switzerland and Belgium.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.
Good deal man. Glad you got it fixed (for the most part anyway).
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.
RTM versions of the .Net framework are SxS compatible with previous version of the framework. As far as I’m aware, even the Beta versions of the .Net framework are SxS compatible with previous versions of the framework. However, Beta versions of framework 3.5 are not SxS compatible with the RTM version of .Net 3.5. See this article[^] for more info. However, that doesn’t appear to be the problem you’re experiencing. KB922271[^] talks about a problem where the ‘Copy Local’ setting in Visual Studio projects causes an issue with MSBuild.exe. Is that the problem you’re having? I know it’s frustrating when a hotfix isn’t publicly available and luckily that isn’t the case for all hotfixes. When Microsoft makes a hotfix available only through professional services this is usually because they don’t want the hotfix widely distributed. Why? Because hotfixes are eventually rolled into larger service packs or fixed before a product is released to market. Even when a fix is publicly available they’re usually accompanied by a message like: “A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.” The issue you’re having is likely already addressed in the release version of Visual Studio 2008, which is currently available on MSDN. I know VS takes a while to install / uninstall (I was just at the Houston InstallFest last night), so when you’ve got some time you might try it again with the RTM version. I hope it works for you.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.
Are you trying to do a full-screen application? If so, are you leveraging the SHFullScreen API? http://msdn2.microsoft.com/en-us/library/aa453694.aspx[^] http://www.pocketpcdn.com/articles/fullscreen.html[^] This can get a bit tricky since SHFullScreen doesn't actually hide the start menu and command bar, it just sets them below your window in the Z-order. Therefore, if you show a new window you may have to adjust the z-order again. It's a bit tricky, but hopefully one of those articles above will help.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Mobile device development is not difficult at all to get started at. VS2005 will work great, but I highly recommend you check out Visual Studio 2008 which just hit RTM not that long ago. VS 2008 supports .Net 2.0, 3.0 and 3.5 on the desktop and 2.0 or 3.5 on the mobile device right out of the box. You do File -> New Project -> Smart Device -> Smart Device Project. The wizzard will then ask you what your target platform is (Pocket PC 2003, WM5, WM6, etc) and what type of project. You can test your project with the built-in emulator, or if you have your device conneted throug ActiveSync (XP) or Sync Center (Vista) you can run your program and debug it right on the device. You can even set breakpoints and do variable evaluation just like you would a local desktop .Net app. The only additional things you might need to download are device-specific skins for the emulator. But that's only if you want the emulator to look like your device and be able to simulate hardware button presses, etc. If you're debugging on the actual device that's not required. There are a lot of great 'getting started' videos available here: http://msdn2.microsoft.com/en-us/netframework/bb495180.aspx[^] Some great tutorials here: http://netcf2.blogspot.com/[^] And finally, a great starting reference here: http://samples.gotdotnet.com/quickstart/compactframework/[^] Good luck!
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Paul's right. Vista and Server 2008 are the last operating systems that will support the VB6 runtime. We are strongly urging ISVs to migrate to .Net if they still have VB6 products.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Ha ha ha. I just realized you only needed the rounded rectangle and I took you all the way to the rounded window. Oh well, all you needed was the CornerRadius bit. And I think you even wrote an article already? Well, good job!
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
You can do it, but you have to get a bit tricky. The window border itself can’t be changed, but you can make a borderless window with a shape inside of it that does what you want. You then have to enable dragging the ‘window’ based on dragging its contents, but it’s not a big deal. Start by setting the following styles on the window: WindowStyle="None" Background="{x:Null}" AllowsTransparency="True" ResizeMode="NoResize" Inside this window you’ll need to place a Border object. Inside the Border you can place whatever you want. Now on the Border set its CornerRadius to something like CornerRadius="0,22,0,22" and set your fill and stroke as desired. Finally, you’ll need to be able to reposition the window regardless of where the user clicks. Fortunately WPF lets you capture events both on the way down (Preview) and on the way back up through the element stack (Element). So to complete your project, in your window class add the following code: protected override void OnMouseLeftButtonDown(MouseButtonEventArgs e) { base.OnMouseLeftButtonDown(e); DragMove(); } And that’s it. You can use this trick for creating windows of literally any shape. Even animation should be supported, though I haven’t tried it. Disclaimer: I’ve only tried this on Vista. I think it SHOULD work on XP, but the Desktop Window Manager in Vista may make a difference.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Ah, much better. Thanks for pointing that out. I'm going to use that from now on in my SequentialWorkflow console demos!
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
The overload of Directory.GetFiles that takes a SearchOption is only available in .Net 3.0 or later, though I agree it's the best option. Note that this can still take a long time and should still potentially be run on a separate thread.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Actually, Application.DoEvents isn't really the best way to handle that. You're absolutely right that the application should yield to the UI thread so the application remains responsive, but Application.DoEvents forces the application message pump to run and isn't recommended. Ideally the code above should be performed on a separate thread from the main UI thread. There are many ways to do that including creating a new thread, using the ThreadPool or asynchronous execution of a delegate (delegate.BeginInvoke / EndInvoke). But one of the coolest ways to execute code off the UI thread is the Dispatcher class. You can use the Dispatcher to execute code with various priority levels and even postpone execution until the application is idle. Note that Dispatcher is new to .Net 3.0, so if you're tied to 1.x or 2.0 then you won't be able to use it. You can read about the Dispatcher here[^]. Unfortunately, once this code is running on a separate thread you still have to get back to the UI thread to update controls. If you have a listbox, for example, and you want to add a ListboxItem for each file you find you won't be able to do it from the worker thread. You can get around that using Control.Invoke, but there's an even easier way if you're in .Net 3.0 or later. That's the BackgroundWorker[^] component, which will help you in easily setting up the background thread to execute your code and even gives you a very easy way to communicate back to the UI thread. BackgroundWorker is certainly the easiest, but if it's too restrictive for what you're trying to do make sure you check out some of those other options. Regards, Jared Bienz
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
No problem at all. The secret to becoming a successful developer is being resourceful and not giving up. Glad I could help.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
First off, Welcome to Programming C#! It's my favorite language. There are a handfull of issues, but at least you gave it the good old college try. :) Let's get started: You were missing a close curly brace at the end, though that could have simply not made it to your clipboard. Next, (and this was the 'Identifier Expected' issue) in DspAvg you didn't define the data type for num1 num2 or num3. You must specify that they're double. After that, in DspAvg you also can't mark those parameters as 'out' because DspAvg never assigns them a value -- it just prints them on the screen. The 'out' keyword signifies that a value will be assigned to the parameter before the method returns. The same thing happened in CalcAvg. No need to mark them as 'out' since they're not being assigned in the method. In CalcAvg you explicitly cast avgNum to a double, which isn't necessary since avgNum is defined as a double at the beginning of the method. It'll still compile, but it's unecessary. Now, here it get's a little interesting. :) DspAgv is marked to return a double, but no value is returned (and one shouldn't be because you're just displaying the results). However, your CalcAvg method doesn't return a value and of course it really should. In Main it looks like you were trying to use DspAvg to show the collected values, but DspAvg requires a fourth parameter (the calculated average). You could either remove that parameter or not use DspAvg until you've done the calculation. In Main, when you call CalcAvg you'll need to store the return value. You should probably have a Console.ReadLine at the end or the window will close before you see the results (if debugging in Visual Studio). Here are the changes, hope it works for you. Now please don't expect another free homework assignment, but DO enjoy learning C#. :laugh: using System; using System.Collections.Generic; using System.Text; namespace Program10 { class Program { static void GetNums(out double num1, out double num2, out double num3) { Console.Write("Enter first number: "); num1 = double.Parse(Console.ReadLine()); Console.Write("Enter second number: "); num2 = double.Parse(Console.ReadLine()); Console.Write("Enter third number: "); num3 = double.Parse(Console.ReadLine()); } static double CalcAvg(double num1, double num2, double num3) { double avgNum; avgNum = num1 + n
Petes article above is a great place to start. You might also want to dive into the .Net Remoting Overview[^] section on MSDN. Specifically there's a good article titled Building a Basic .NET Framework Remoting Application[^] I'd also like to make sure you're aware of Windows Communication Foundation (WCF). You may have a business reason for using Remoting so I wanted to provide those resources, but if this is a hobby project or you’re starting new product development you really should consider using WCF instead. .Net Remoting will be around for a long time yet, but Microsoft is no longer developing that technology and WCF is the recommended platform for all new communications development. WCF will still let you do the same things that Remoting will (cross-process communication, fast binary encoding, singletons, serialization, etc.) but it will also let you do so much more. A WCF service can be hosted in-process like a Remoting service can, but it can also be hosted, activated and load balanced on an IIS server. WCF allows the same service instance to be contacted over a binary TCP channel, a SOAP web service channel, a named pipe or even a message queue -- all without changing a single line of code. How a service behaves, how security is applied and how a service communicates can all be described in code or alternatively in an XML configuration file without needing to recompile the application. You can even use WCF to write P2P applications! If you'd like to check out WCF I recommend you start with http://wcf.netfx3.com[^] or the Windows Communication Foundation[^] area on MSDN. I hope you find what you're looking for, and happy coding! Jared
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.