sqlazureexplorer Discussions Rss Feed

New Post: Is SQL Azure Explorer available by default

mysorian — Wed, 28 Apr 2010 22:30:17 GMT

I would like to know if SQL Azure Explorer is available by default in

Microsoft Visual Studio 2010 Ultimate, Version 10.0.30128.1 RC1Rel

How do I check in the VS2010 IDE if an add-in is installed?

Is there an update after the release of VS 2010 Ultimate such as the one I am using.

New Post: Azure Explorer is not visible

johandanforth — Fri, 18 Dec 2009 14:03:16 GMT

And it seems to work too from what I heard from @grapesfrog.

New Post: Does it work with VS2008 SP1?

mysorian — Mon, 14 Dec 2009 18:26:41 GMT

Thanks.

New Post: Feedback & Ideas

johandanforth — Mon, 14 Dec 2009 17:21:00 GMT

Hi Mark (I guess it is :)

Not sure I understand the prob fully. You say SQL Azure is not working with .NET 4.0, but this whole VS addin is written in VS2010 and .NET 4.0 so I'm a bit confused :)

The connection you mention, is that the properties window in the SQL Azure Explorer addin or elsewhere?

Can you please explain in more detail what you tried to do, and I'll update my directions!

Cheers too you too,

Johan

New Post: Does it work with VS2008 SP1?

johandanforth — Mon, 14 Dec 2009 17:15:41 GMT

Yes, it's for VS2010 (beta 2 right now) only, I hope I've written that everywhere. If I forgot to mention it somewhere, please let me know.

/Johan

New Post: Feedback & Ideas

CSharpMark — Sun, 13 Dec 2009 23:05:20 GMT

Great tool after I got it to work. After scratching my head for hours and surfing for solutions I found that SQL Azure doesn't yet work with .NET 4.0 and that is only supported with .NET 3.5. The other problem was getting a connection, which is done through the SQL Azure Properties window. I recommend that you add those items to your directions. Cheers!

New Post: Does it work with VS2008 SP1?

mysorian — Sun, 06 Dec 2009 22:50:17 GMT

Looks like it is for VS2010.

New Post: Azure Explorer is not visible

johandanforth — Tue, 20 Oct 2009 11:27:19 GMT

Good idea, I just installed beta 2 and noticed the same thing when running as admin now so I had to run vs as a "normal" user. Thanks Rob.

/Johan

New Post: Azure Explorer is not visible

Rob71 — Tue, 20 Oct 2009 11:14:29 GMT

nickrandolph wrote:

Are you running Visual Studio "as administrator". I noticed that if I did that the tools item wasn't there, nor was the entry in the view, other windows menu etc

I had this same problem, when running vs2010 "as administrator" couldn't see it, when running normally could see it in both places.

Try Tools > Environment > Extension Manager ... make sure "Load extensions from my local application data folder" is checked ..... this worked for me (i'm using VS2010 beta1 and Windows 7 RC)

Cheers ... Rob.

New Post: Azure Explorer is not visible

johandanforth — Thu, 08 Oct 2009 17:50:47 GMT

I'm not sure what to do other than maybe re-install it and try again, checking the event log for any hints or ask the guys at the VS2010 Beta 1 extensibility forum -> http://social.msdn.microsoft.com/Forums/en-US/vsxprerelease/threads

What version of VS2010 are you using? Team Suite?

New Post: Azure Explorer is not visible

susai — Thu, 08 Oct 2009 15:52:00 GMT

I am using Windows XP SP3

I have Administrator privilege in my computer. Let me know if any other way I can fix this issue.

Thanks

New Post: Azure Explorer is not visible

johandanforth — Thu, 08 Oct 2009 09:40:23 GMT

Strange indeed.

I'm on Win7 RC (still), and I've actually never had any problems seeing the SQL Azure Exploreer "menu item" in either menu, no matter if I was running as administrator or as normal user. What OS are you on Susai and have you tried different access levels (as administrator and not)?

New Post: Azure Explorer is not visible

nickrandolph — Thu, 08 Oct 2009 09:02:26 GMT

Are you running Visual Studio "as administrator". I noticed that if I did that the tools item wasn't there, nor was the entry in the view, other windows menu etc

New Post: Azure Explorer is not visible

susai — Wed, 07 Oct 2009 21:00:38 GMT

I have installed vs2010 and Sql Azure Explorer.

Even my extension manager says its installed but I am not able to open the explorer through the view/other windows nor from tools menu..

Let me know from where I can invoke the explorer.

Thanks

New Post: Issues connecting to SQL Azure

johandanforth — Sat, 03 Oct 2009 13:14:49 GMT

I don't know about integration/merging of projects, perhaps! This tool is just something fun I started to learn more about the bits, but we could try and contact the migration wizard people and hear what they say.

I'm thinking of adding some simple functionality to manage logins.

New Post: Issues connecting to SQL Azure

nickrandolph — Sat, 03 Oct 2009 13:03:13 GMT

I was just using the administrator account for the server, rather than an additional restricted user. It would be great to see some of the functionality of the sql azure migration wizard integrated into your work. Any chance the projects could be merged?

Nick Randolph | Built To Roam | Microsoft MVP - Device Application Development | +61 412 413 425
The information contained in this email is confidential. If you are not the intended recipient, you may not disclose or use the information in this email in any way. Built To Roam does not guarantee the integrity of any emails or attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Built To Roam.

From: johandanforth [mailto:notifications@codeplex.com]
Sent: Saturday, 3 October 2009 11:01 PM
To: Nick Randolph
Subject: Re: Issues connecting to SQL Azure [sqlazureexplorer:70882]

From: johandanforth

I think it depends on which user you are connecting with. I've mostly used the default "admin" so far, without having to use the username@servername format, so I'm not sure why you'd have to use that format. MSDN has these things to say about SQL Azure users:

Because some tools implement tabular data stream (TDS) differently, you may need to append the SQL Azure server name to the login in the connection string using the <login>@<server> notation. In these cases, separate the login and SQL Azure server name with the @ symbol. For example, if your login was named login1 and the fully-qualified name of your SQL Azure server is servername.ctp.database.windows.net, the username parameter of your connection string should be: login1@servername. This restriction places limitations on the text you can choose for the login name. For more information, see CREATE LOGIN (SQL Azure Database).

Are you using a user/login you created or the default administrator? I still have some work to do on the error handling for using logins with restricted access...

Read the full discussion online.

To add a post to this discussion, reply to this email (sqlazureexplorer@discussions.codeplex.com)

To start a new discussion for this project, email sqlazureexplorer@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

New Post: Issues connecting to SQL Azure

johandanforth — Sat, 03 Oct 2009 13:00:30 GMT

Are you using a user/login you created or the default administrator? I still have some work to do on the error handling for using logins with restricted access...

New Post: Issues connecting to SQL Azure

nickrandolph — Sat, 03 Oct 2009 12:18:36 GMT

Actually, the first error I got was the following. I read this to indicate that the server should just be "servername" - I got it to work on one machine by extending this to the full dns name. On the other machine I then needed to follow the second part of the error message message which says that the user name should include the servername. I should have realised this as other SQL Azure tools sometimes require this in order to connect. Best practice IMHO is to use the full server dns name and the username@servername format for the username.

---------------------------
Ops! Problems!
---------------------------
Exception getting data from SQL Azure, have you set your credentials? Server name cannot be determined. It must appear as the first segment of the server's dns name (servername.ctp.database.windows.net). Some libraries do not send the server name, in which case the server name must be included as part of the user name (username@servername). In addition, if both formats are used, the server names must match.
---------------------------
OK
---------------------------

All up and running now, so all good, thanks.

New Post: Issues connecting to SQL Azure

johandanforth — Sat, 03 Oct 2009 09:22:44 GMT

Hi and thanks for trying out the app. That's weird, but I've noticed that sometimes SQL Azure itself is not available. I've seen that happen a couple of times, then I tried a few minutes later and it worked.

It's a pretty ordinary SqlConnection so my guess it's either SQL Azure is down, a firewall or something stopped the network traffic to Azure or perhaps you need to re-check your settings again and make really sure you got the right servername and such. I don't know if there's any limitation to the number of connections you can have for your SQL Azure account, but I've never heard about such limits.

How many databases have you got created? Using any "unusual" characters for login or database names? (just thinking of odd things here :)

New Post: Issues connecting to SQL Azure

johandanforth — Sat, 03 Oct 2009 09:22:44 GMT

How many databases have you got created? Using any "unusual" characters for login or database names? (just thinking of odd things here :)