We do make developers live harder!

[G. Tarazi]

After spending years of software development using the Microsoft products, I realized the following "If a development tool was not built by the VS.NET or the SQL Server teams, it will make your live harder".



The first example is BizTalk 2004, but I won't talk about it here.



The second one is some of the InfoPath limitations, and one of them is the security exceptions.



I am developing a form using VS.NET / C# / and InfoPath

I am trying to use the "thisXDocument.UI.ShowModalDialog" method.

I signed the form.

And using VS.NET I tried to open it in debug mode to test the code.



And suddenly an error message, which is attached, saying that the form cannot be signed, must be published and then used.



And of course this result in: System.Security.SecurityException



Which is total nonsense, it is under development, the form must have full access to the resources, I chose that, why it just can't do it?



Now, I will lose an hour or 2 testing my code; republishing my form all over, just because I can't find a way to get a form that is under development to be trusted!



I appreciate the fact that your are trying to protect me, but should I be protected from myself



Here is the difference between the SQL Server / VS.NET teams and the rest of the teams at MS; they will never surprise you with something weird like that.

 

[G. Tarazi]

Attached
"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message After spending years of software development using the Microsoft products, I realized the following "If a development tool was not built by the VS.NET or the SQL Server teams, it will make your live harder".



The first example is BizTalk 2004, but I won't talk about it here.



The second one is some of the InfoPath limitations, and one of them is the security exceptions.



I am developing a form using VS.NET / C# / and InfoPath

I am trying to use the "thisXDocument.UI.ShowModalDialog" method.

I signed the form.

And using VS.NET I tried to open it in debug mode to test the code.



And suddenly an error message, which is attached, saying that the form cannot be signed, must be published and then used.



And of course this result in: System.Security.SecurityException



Which is total nonsense, it is under development, the form must have full access to the resources, I chose that, why it just can't do it?



Now, I will lose an hour or 2 testing my code; republishing my form all over, just because I can't find a way to get a form that is under development to be trusted!



I appreciate the fact that your are trying to protect me, but should I be protected from myself



Here is the difference between the SQL Server / VS.NET teams and the rest of the teams at MS; they will never surprise you with something weird like that.

 

[Josh Bertsch [MSFT]]

Check this thread out:

http://groups.google.com/groups?hl=...7IiYhyKEHA.1032%40tk2msftngp13.phx.gbl&rnum=4

--josh bertsch
"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message Attached
"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message After spending years of software development using the Microsoft products, I realized the following "If a development tool was not built by the VS.NET or the SQL Server teams, it will make your live harder".



The first example is BizTalk 2004, but I won't talk about it here.



The second one is some of the InfoPath limitations, and one of them is the security exceptions.



I am developing a form using VS.NET / C# / and InfoPath

I am trying to use the "thisXDocument.UI.ShowModalDialog" method.

I signed the form.

And using VS.NET I tried to open it in debug mode to test the code.



And suddenly an error message, which is attached, saying that the form cannot be signed, must be published and then used.



And of course this result in: System.Security.SecurityException



Which is total nonsense, it is under development, the form must have full access to the resources, I chose that, why it just can't do it?



Now, I will lose an hour or 2 testing my code; republishing my form all over, just because I can't find a way to get a form that is under development to be trusted!



I appreciate the fact that your are trying to protect me, but should I be protected from myself



Here is the difference between the SQL Server / VS.NET teams and the rest of the teams at MS; they will never surprise you with something weird like that.

 

[G. Tarazi]

I give-up, I am not popping up external windows anymore, just using another web page in the task panel, it does some of the job.



It's probably possible to debug the fully trusted form, but I don't recommend it if your time costs money, prepare yourself to lose 3 days of trying until you get the idea behind it; instead of just having a check box some ware that enables us to debug a fully trusted form.



"Developing a check box that allows you to debug a fully trusted form, costs couple of thousand; making sure that every developer must lose 3 days of work in order to figure out how to do it manually; priceless " , and for everything else, there is ...


"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message I did that (attached image) and it's still not working :-(

Check this thread out:

http://groups.google.com/groups?hl=...7IiYhyKEHA.1032%40tk2msftngp13.phx.gbl&rnum=4

--josh bertsch
"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message Attached
"G. Tarazi" <Tarazi (at) LiveTechnologies.ca> wrote in message After spending years of software development using the Microsoft products, I realized the following "If a development tool was not built by the VS.NET or the SQL Server teams, it will make your live harder".



The first example is BizTalk 2004, but I won't talk about it here.



The second one is some of the InfoPath limitations, and one of them is the security exceptions.



I am developing a form using VS.NET / C# / and InfoPath

I am trying to use the "thisXDocument.UI.ShowModalDialog" method.

I signed the form.

And using VS.NET I tried to open it in debug mode to test the code.



And suddenly an error message, which is attached, saying that the form cannot be signed, must be published and then used.



And of course this result in: System.Security.SecurityException



Which is total nonsense, it is under development, the form must have full access to the resources, I chose that, why it just can't do it?



Now, I will lose an hour or 2 testing my code; republishing my form all over, just because I can't find a way to get a form that is under development to be trusted!



I appreciate the fact that your are trying to protect me, but should I be protected from myself



Here is the difference between the SQL Server / VS.NET teams and the rest of the teams at MS; they will never surprise you with something weird like that.