I'm just starting with windows phone development and was trying to get the datePicker to work. Searching for tutorials, all seem to be pointing to a reference to
C:\Program Files (x86)\Microsoft SDKs\Windows
Phone\v7.0\Toolkit\Nov10\Bin\Microsoft.Phone.Controls.Toolkit.dll
The problem is that i don't have this file (and after a computer search this file doesn't exist at all in my computer) so after looking some more, a found this link that says that i must install the toolkit. This seems quite not right(i was thinking this feature was fully integrated, not a alternate design being such a key-feature).
Analysing the feed i got from google, those link are pretty old(september - november 2010). Has Microsoft redesigned the method to acces dataPicker or is this method still the current official one?
I'm not fully sure of the reason but from the codeplex page:
Straight from Microsoft, both the Silverlight Toolkit and Silverlight
for Windows Phone Toolkit provide the developer community with new
components, functionality, and an efficient way to help shape product
development. Toolkit releases include open source code, samples &
docs, plus design-time support for the Windows Phone platform as well
as the Silverlight browser plugin.
The easiest way to pick and choose what components to install is probably via NuGet.
http://nuget.org/List/Packages/SilverlightToolkitWP
This is more or less the current way. The main changes are that there's now an easier way of getting the toolkit using NuGet and there is a later release that supports WP7 Mango.
I'd recommend getting the sample app so you can see good examples of Toolkit however.
Just download and install the Toolkit which is readily available in the following link,
Silverlight Toolkit.
Then Add reference to the Microsoft.Phone.Controls.Toolkit.dll in the installed folder.
Then you can access it with adding the xaml code,
xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
Related
I am trying to develop an Add-In for Microsoft Word on macOS. The Windows version of the Add-In is already in development, but I don't have access to its source code. It seems like the following is the 'landing' page for developing Add-Ins for Office:
https://learn.microsoft.com/en-us/office/dev/add-ins/
The above documentation seems to say that Add-Ins have to developed using web-technologies, and, upon examination of existing, Third-party, Add-Ins, this seems to be the case at least for the UI. What I don't understand, is, if the entire plugin has to be written using web-oriented languages, or if there is a macOS oriented SDK that allows to implement at least the underlying logic using a macOS native SDK, perhaps using Objective-C or Swift. I was hoping that somebody more expert could bring me in the right direction. Thanks for your attention.
There is no platform specific SDK for developing Office add-ins. You can use web technologies for developing cross-platform Office add-ins, see https://learn.microsoft.com/en-us/office/dev/add-ins/overview/office-add-ins for more information.
You also can use AppleScript for automating tasks in Word on the MacOS.
I've been trying to install VSCommunity Edition for the last few hours with no luck. If you check the screenshot attached. You'll see that I can change the directories for installation for the first 2 requirements, but im unable to change the directory for the 3rd option (the SDK install along with others) which just happen to be the very large percentage of files. It's wanting to install over 45gb of files on my C Drive which is just a 50gb SSD.
enter image description herehttps://i.imgur.com/burFR90.jpg
I want to switch to D, and the only thing i can see fro any of the Microsoft help docs and posts is "You can change this upon fresh installation".
Which this is. I've uninstalled anything else remotely like it just to be sure.
Do any of you have any ideas or any experience with this issue, or anything i can try? I simply don't have enough space to install on C, and because of this, i can't start learning c# which is required for work.
Thanks so much in advance guys, it's really getting me worried now.
Although I can only guess why Visual Studio is locking down the SDK path, here's a few workarounds and recommendations:
In your screenshot, the installer warns you about possible performance effects of installing Visual Studio on your D drive. I assume this is because your D drive is not an SSD. Microsoft's Visual Studio system requirements document recommends that you install to an SSD, and based on community experience, this is one recommendation you really want to stick to, otherwise IDE responsiveness may be well below your expectations, especially if you decide to install extensions in future.
Instead, you might want to reconsider the set of components that you're installing. If you're only getting started with C#, you'll probably be just fine with developing class libraries, console and web applications targeting .NET Framework or .NET Core. If this is the case, you might want to go to the Workloads tab in the installer and opt out of some of the heaviest workloads (such as Mobile development with .NET). Consider only installing .NET desktop development, ASP.NET and web development, Azure development and .NET Core cross-platform development. If you only select these, your installation is going to be much slimmer.
If minimizing Visual Studio installation as shown above isn't enough, consider an alternative way of setting up your .NET development environment. For example, you can download and install .NET Core SDK and .NET Core Runtime, and use one of the two most prominent alternative code editors: Visual Studio Code or JetBrains Rider that are both quite compact.
I'm attempting my first crack at a PCL, targeting Windows, WinPhone and Xamarin. I'm finding that some very basic things, like Package and SortedDictionary, won't import (claims they don't exist). I'm sure this exists in Windows and Xamarin (Mono), so I'm a bit lost as to why my Imports doesn't work. Perhaps it's because Xamarin included Silverlight and SL doesn't support it?
Can anyone point me to a big list of supported imports that might help? Or perhaps a comparison tool? There's a scanner tool on the Xamarin web site, but it appears to be broken. I can't find a list on the Xamarin site, and my google-fu has once again failed me.
Here are some features listed, albeit not including Xamarin. OTOH Xamarin is very feature rich and it is unlikely that something is missing because of it. More likely the culprits are Silverlight and WP Silverlight.
You can also try the .NET Portability Analyzer.
I've been reading a lot into this and MonoMac/Mono seemed to be the best if not one of the only ways to go about it. I do have a MacBook Pro and it seems Xamarin bought Mono and wants something like $800 for a business edition to be able to load in Visual Studio projects. I only downloaded the free version so when I tried to load in my VS project on my Mac into Xamarin it said it didn't recognize it and that's when I discovered it seemed I needed a business edition.
A lot of what my search found was stuff that was 1-2 years old and even older. Things seemed to have changed a bit since then and with the Xamarin integrating Mono sort of thing. I've been working on an XNA 4.0 game for PC for over 7 months now and I'd like to have a Mac version. Apparently games like Magicka have figured it out and were made in XNA. I plan to release on Steam so I suppose I need to find a way to try and make it work with Steam if that's possible too. I don't really use my MacBook that often and I don't have Steam on it so I'm not really sure how to go about this.
I guess it comes down to this. I don't understand the current situation of MonoMac and Xamarin and did they aquire Mono? Do I need that expensive business edition? Are there alternatives? How does this tie in to being able to release a Mac version on Steam?
Most of the information I can find is a few years ago now and a lot has changed it seems.
MonoGame is a re-implementation of the XNA API for various platforms, including Mac.
It depends on Mono to provide a C# runtime across different platforms. And on platform specific versions of Mono (such as MonoMac, MonoTouch, etc, from Xamarin) to provide the API bindings and other features specific to those platforms.
You don't so much "load" an existing Visual Studio project as create a new project - either in Visual Studio (if the tools are available and you've bought them - but I don't think this is the case for Mac) or MonoDevelop or Xamarin studio.
To your new project, you would add your existing source files and add a reference to the MonoGame library for that platform. That MonoGame library will provide versions of the classes in the Microsoft.Xna.Framework namespace that work on that platform. Your code gets compiled against these alternate classes, creating a new binary specific for that platform.
(MonoGame will probably have more in-depth documentation of the process on their website, including how to deal with game content.)
Put simply: Use MonoGame. It is an alternate version of the XNA library, not a conversion tool.
In my latest WP7 project I added using Nuget a reference to the Silverlight Toolkit for WP7.
In one of my pages I added a new namespace reference at the top as I've done on previous occasions:
xmlns:toolkit="clr-namespace:System.Windows.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
However, when I try to add a toolkit control to the page, I get only one option after typing
<toolkit:HeaderedItemsControl
All the other toolkit controls are not accessible from XAML.
Did anyone face any similar issues with the lastest Nuget release for Silverlight Toolkit on WP7?
Am I missing something (I've used the toolkit before without any issues... although I agree I didn't use Nuget on that occasion)?
I can access the other toolkit classes from code without any problems...
Any help or suggestions are welcomed!
Thank you in advance!
Andrei